Thread-exit hang via lost worker teardown signal
Published Nov 2, 2026 · Updated Nov 2, 2026
Signal loss in Linux io_uring/io-wq allows local users to hang an exiting thread through an asynchronous FIFO open. In io_worker_handle_work(), task-work processing clears TIF_NOTIFY_SIGNAL before pending bounded work starts, losing the teardown signal sent by io_wq_exit_workers(). The trigger requires io_uring access, an IOSQE_ASYNC open of a FIFO without a writer, and exit of the submitting thread; the documented consequence is a thread stuck in do_exit(), not a system crash.
Summary
What happened
Signal loss in Linux io_uring/io-wq allows local users to hang an exiting thread through an asynchronous FIFO open. In io_worker_handle_work(), task-work processing clears TIF_NOTIFY_SIGNAL before pending bounded work starts, losing the teardown signal sent by io_wq_exit_workers(). The trigger requires io_uring access, an IOSQE_ASYNC open of a FIFO without a writer, and exit of the submitting thread; the documented consequence is a thread stuck in do_exit(), not a system crash.
The record
- CVE
- CVE-2026-99228
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 2026Record 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.12
- Affected versionversion=afcc4015d1bf5659b8c722aff679e9b8c41ee156 <08c42055b8f9a5d29236d34ad4bce08828239fe1
- Affected versionversion=afcc4015d1bf5659b8c722aff679e9b8c41ee156 <62996803c1b5f18176de255db4c843021f2d19c8
- Affected versionversion=afcc4015d1bf5659b8c722aff679e9b8c41ee156 <7309fea05a3d66af9746843c43fef14c10b8141e
- Affected versionversion=afcc4015d1bf5659b8c722aff679e9b8c41ee156 <ddccc60f036b309430cf130d48aafed94ef7355a
- Affected versionversion=afcc4015d1bf5659b8c722aff679e9b8c41ee156 <fdb771015c1e13677b57a4015f0c938748f13781
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us