CVE-2026-99804: io_uring/io-wq: save worker type before dropping its reference
In the Linux kernel, the following vulnerability has been resolved:
iouring/io-wq: save worker type before dropping its reference
iowqcanceltwcreate() inspects cb->func after calling ioworkercancelcb(). For an existing worker, that call can drop the last worker reference and wake ioworkerexit(). If the canceling task is preempted, the worker can be unlinked and freed by kfreercu() before the callback function is inspected. KASAN reports a slab-use-after-free read in this path.
Save whether the callback belongs to an unpublished continuation worker while its reference is still held, then use the saved result for the conditional free. This preserves the existing accounting and frees only the worker allocated for the canceled continuation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.11 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.16 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.2 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1
Frequently Asked Questions
What condition is required to trigger the use-after-free?
The issue occurs when io_wq_cancel_tw_create() cancels a callback for an existing worker and then examines cb->func after io_worker_cancel_cb() may have released the final worker reference. Exploitation requires the worker-exit path to unlink and free the worker before that later callback inspection.
What is the observable impact of this flaw?
The reported symptom is a KASAN-detected slab use-after-free read. The vulnerable path can dereference callback data after the associated worker has been freed through kfree_rcu().
What does the fix change?
The fix records whether the callback belongs to an unpublished continuation worker before dropping the worker reference. It then uses that saved value to decide whether to free the canceled continuation worker, preserving the existing accounting behavior.