In the Linux kernel, the following vulnerability has been resolved: io-wq: order the exit bit against worker creation task work…
CVE-2026-99243
In the Linux kernel, the following vulnerability has been resolved: io-wq: order the exit bit against worker creation task work iowqexitworkers() cancels task work for queued worker creation with taskworkcancelmatch(). That has a plain load of task->taskworks. ioqueueworkercreate() adds the new entry and tests IOWQBITEXIT to cancel it if the workqueue is already on its way out. That must be ordered. taskworkadd() has a full barrier via cmpxchg(). But iowqexitstart() sets the bit with setbit() which doesn't have any memory ordering. So afaict, on weakly ordered architectures the exiting task may load taskworks before the store of the bit is visible. The other side tests the bit before the store is visible as well. So the entry remains queued with workerrefs and the exiting task waits on workerdone indefinitely. If the task still has rings then iouringdeltctxnode() provides the barrier via testandsetbit() in iowqsetexitonidle(). When it has closed all rings though that barrier is gone. Add the barrier after the setbit().
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 3 November 2026
- Last updated
- 3 November 2026
- Assigner
- Linux
At the source
References
- https://git.kernel.org/stable/c/67da3eec264aeb67835886720243ae2dc1463315
- https://git.kernel.org/stable/c/a63c752157eacf49f628359822666b32503d194a
- https://git.kernel.org/stable/c/1432d881d99584105122760133caeff1dce7a9f7
- https://git.kernel.org/stable/c/6cf012a4d5e461c788ecc9dbed67adc31a142644
- https://git.kernel.org/stable/c/0d81cdd433b0a96c5275c01b8172e0b1f71dd595
- https://git.kernel.org/stable/c/75395db7a9b40a2e826c838e648fef8ed1a2d174
- https://git.kernel.org/stable/c/31fc780b75b278d37700373d54a99fdb4117fdd6
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99243