CVE-2026-99231
Description
In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: own the request before clearing ->head io_waitid_remove_wq() only takes the wait queue lock if ->head is set. io_waitid_wait() clears ->head first thing, before it tries to become the owner of the request by bumping ->refs. If somebody else owns the request at that point, nothing keeps it from completing the request while the wake up handler is still going to touch it: CPU0 (io_waitid_wait) CPU1 (io_waitid, holds a ref) list_del_init(&wait->entry) smp_store_release(&iw->head, NULL) __do_wait() finds another child io_waitid_remove_wq() // ->head == NULL, no locking io_waitid_finish(), IOU_COMPLETE // request freed and reused atomic_fetch_inc(&iw->refs) The same goes for __io_waitid_cancel() if it claims the request in that window. ->refs is part of the per opcode data of the request, so this increments whatever the next user of the request keeps there. If that happens to be zero, the handler concludes that it owns the request, and queues io_waitid_cb() for it. With the window held open by a delay, and the request reused for a receive that is waiting for data: BUG: KASAN: slab-use-after-free in __wake_up_common+0x1ca/0x1f0 __wake_up_sync_key+0x36/0x50 sock_def_readable+0xf1/0x420 unix_stream_sendmsg+0x60b/0x1110 Allocated by task 87: io_arm_apoll+0x1ed/0x940 Freed by task 87: __io_submit_flush_completions+0x118d/0x1a10 tctx_task_work_run+0x327/0x950 Only clear ->head once the handler owns the request. If it doesn't, the owner finds ->head set and has to wait for the lock, which is held by the caller of the handler. Deleting the already deleted entry again is harmless.
Timeline
- 2026-11-02Published by the CNA16:06 UTC
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux | from 6.12.113 before 6.12.115fixed in 6.12.115from 6.18.52 before 6.18.60fixed in 6.18.60 | 6.12.1156.18.60 |
| linux linux_kernel | from 6.12.113 before 6.12.115fixed in 6.12.115from 6.18.52 before 6.18.60fixed in 6.18.60from 6.19 before 7.2.14fixed in 7.2.14from 6.19 before 7.3.2fixed in 7.3.2from 6.19 before 7.4-rc1fixed in 7.4-rc1 | 6.12.1156.18.607.2.147.3.27.4-rc1 |
References
- https://git.kernel.org/stable/c/6e11ce129b34fb9a43b2bbe838df49ea52878d5c
- https://git.kernel.org/stable/c/8381a912c65b8de16e8a848225c7c5a56b6ea834
- https://git.kernel.org/stable/c/bf01da1a9cca4a54e5c30b8344e52c26afb87be7
- https://git.kernel.org/stable/c/c10ad2813e15186fb51b37a4d17fafddc99e89a5
- https://git.kernel.org/stable/c/c254eec4364b9f4b4cbdce43be3fb4df5a651a70
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-99231'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-99231'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-99231'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-99231'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).