CVE-2026-99800: io_uring: free the task context after a grace period

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iouring: free the task context after a grace period

A task other than the owner can free a request, ioringexitwork() running the local taskwork of a DEFERTASKRUN ring for example, or iodoiopoll() reaping completions. ioputtask() then takes the else branch:

percpucountersub(&tctx->inflight, 1); if (unlikely(atomicread(&tctx->incancel))) wakeup(&tctx->wait); puttaskstruct(tctx->task);

The first line is what lets the owner leave iouringcancelgeneric(), and on exec it frees the tctx right after. Nothing holds that off for the remaining three lines, the task reference only covers a tctx freed along with the taskstruct. It used to work out because iouringdeltctxnode() took the uringlock that the freeing side holds across ioputtask(), until that moved to tctxlock.

Free the tctx with kfreercu(), and enter an RCU read section in ioputtask() before the count is dropped.

Affected Software

3 affected componentsFixes available
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux<7.3.3-1
7.3.3-1
debian/linux
6.1.176-16.1.192-26.12.107-16.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Frequently Asked Questions

1

What conditions are required for this issue to occur?

The affected task context must be released by a task other than its owner while the owner is able to leave io_uring_cancel_generic() and free that context, such as when io_ring_exit_work() runs local task_work for a DEFER_TASKRUN ring or when io_do_iopoll() reaps completions. The race concerns the remaining operations in io_put_task() after the inflight counter is decremented.

2

Is this limited to a particular io_uring configuration or execution path?

The description specifically identifies DEFER_TASKRUN rings whose local task_work is run by io_ring_exit_work(), and completion reaping through io_do_iopoll(), as paths where another task can free a request. No information is provided about whether other io_uring configurations are affected.

3

What does the fix change?

The fix defers freeing the task context with kfree_rcu() and enters an RCU read-side critical section in io_put_task() before decrementing the inflight count. This prevents the task context from being freed while io_put_task() still accesses it.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203