CVE-2026-99243
io-wq: order the exit bit against worker creation task work
In the Linux kernel, the following vulnerability has been resolved: io-wq: order the exit bit against worker creation task work io_wq_exit_workers() cancels task work for queued worker creation with task_work_cancel_match(). That has a plain load of task->task_works. io_queue_worker_create() adds the new entry and tests IO_WQ_BIT_EXIT to cancel it if the workqueue is already on its way out. That must be ordered. task_work_add() has a full barrier via cmpxchg(). But io_wq_exit_start() sets the bit with set_bit() which doesn't have any memory ordering. So afaict, on weakly ordered architectures the exiting task may load task_works 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 worker_refs and the exiting task waits on worker_done indefinitely. If the task still has rings then io_uring_del_tctx_node() provides the barrier via test_and_set_bit() in io_wq_set_exit_on_idle(). When it has closed all rings though that barrier is gone. Add the barrier after the set_bit().
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 4b4e5bbf9386d4ec21d91c0cb0fd60b9bba778ec; < 67da3eec264aeb67835886720243ae2dc1463315 (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < a63c752157eacf49f628359822666b32503d194a (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < 1432d881d99584105122760133caeff1dce7a9f7 (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < 6cf012a4d5e461c788ecc9dbed67adc31a142644 (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < 0d81cdd433b0a96c5275c01b8172e0b1f71dd595 (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < 75395db7a9b40a2e826c838e648fef8ed1a2d174 (affected, git) ≥ 71a85387546e50b1a37b0fa45dadcae3bfb35cf6; < 31fc780b75b278d37700373d54a99fdb4117fdd6 (affected, git) ≥ 5.15.11; < 5.15.224 (affected, semver) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.16 (affected) ≥ 0; < 5.16 (unaffected, semver) ≥ 5.15.224; ≤ 5.15.* (unaffected, semver) ≥ 6.1.191; ≤ 6.1.* (unaffected, semver) ≥ 6.6.161; ≤ 6.6.* (unaffected, semver) ≥ 6.12.115; ≤ 6.12.* (unaffected, semver) ≥ 6.18.60; ≤ 6.18.* (unaffected, semver) ≥ 7.2.14; ≤ 7.2.* (unaffected, semver) ≥ 7.3.1; ≤ 7.3.* (unaffected, semver) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/67da3eec264aeb67835886720243ae2dc1463315CNA: Linux
- https://git.kernel.org/stable/c/a63c752157eacf49f628359822666b32503d194aCNA: Linux
- https://git.kernel.org/stable/c/1432d881d99584105122760133caeff1dce7a9f7CNA: Linux
- https://git.kernel.org/stable/c/6cf012a4d5e461c788ecc9dbed67adc31a142644CNA: Linux
- https://git.kernel.org/stable/c/0d81cdd433b0a96c5275c01b8172e0b1f71dd595CNA: Linux
- https://git.kernel.org/stable/c/75395db7a9b40a2e826c838e648fef8ed1a2d174CNA: Linux
- https://git.kernel.org/stable/c/31fc780b75b278d37700373d54a99fdb4117fdd6CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.