Kernel warnings via interrupt-context fsnotify calls
Published Dec 24, 2025 · Updated Dec 24, 2025
Improper execution context in affected Linux kernel io_uring code allows local users to trigger kernel locking-state warnings. The __io_complete_rw_common path invokes fsnotify access or write handling from kiocb completion, which can run in soft- or hard-interrupt context even though fanotify event handling allocates memory and acquires locks. Triggering requires asynchronous io_uring file I/O with filesystem notification handling; the published record demonstrates a lock-dependency warning but does not establish a crash or broader compromise.
Summary
What happened
Improper execution context in affected Linux kernel io_uring code allows local users to trigger kernel locking-state warnings. The __io_complete_rw_common path invokes fsnotify access or write handling from kiocb completion, which can run in soft- or hard-interrupt context even though fanotify event handling allocates memory and acquires locks. Triggering requires asynchronous io_uring file I/O with filesystem notification handling; the published record demonstrates a lock-dependency warning but does not establish a crash or broader compromise.
The record
- CVE
- CVE-2022-50705
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.18
- Affected versionversion=b436d1e92662adecafff4c95baae6352289c2d80
- Affected versionversion=df1ec53252d5b5b26ea49e30438741c9a6d89857 <89a410dbd0f159ddd308f19d6eb682fc753e4771
- Affected versionversion=dfbe550c8235b7e98284db37eeeddfd3b4b19b00
- Affected versionversion=f63cf5192fe3418ad5ae1a4412eba5694b145f79 <2a853c206e553dd9c0a55c22858fd6a446d93e15
- Affected versionversion=f63cf5192fe3418ad5ae1a4412eba5694b145f79 <b000145e9907809406d8164c3b2b8861d95aecd1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo