CVE-2026-99254

io_uring: don't flood a cancelling task with task_work

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring: don't flood a cancelling task with task_work io_ring_exit_work() asks each task which has used the ring to remove its tctx node, by task_work, and repeats that until the list is empty. io_tctx_exit_cb() doesn't touch the node while the task is in io_uring_cancel_generic(), which removes all the nodes at its end. So the work item queues the callback again as soon as it has completed, for nothing. That is more than a waste of time. task_work_run() only returns when it finds the list empty. If the rings are released from inside the cancellation, because requests of other rings held the last references to their files, up to 64 work items keep sending callbacks to the one task which is running them. It never finds the list empty, never gets back to the cancellation, the nodes stay, and so it goes on: a task with 60 pairs of rings which poll each other ran 280000 callbacks in 5 seconds, 20 seconds after exit_group(). It ends when all the senders happen to be late at the same time. Until then the task keeps a CPU and the work items busy. An exiting task can't be killed meanwhile. execve() cancels the requests in the same way, so a live task can get stuck there as well, for minutes. If it takes more than five, the work items run into the WARN_ON_ONCE(time_after(jiffies, timeout)) of io_ring_exit_work(). No privilege is needed for any of this. If the callback has met a task in cancellation, wait a little before it is sent again. Nobody has to wake the work item up for that: either the node is gone by then, or it is the turn of the next round.

Key facts

Published
3 Nov 2026
Last changed
6 Nov 2026
Assigned by
Linux
EPSS
0.197% likely to be exploited in the next 30 days, higher than 9.474% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding a22fb44e988b01b82235ea07f0bf0fc73e256596 (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding 2c75ebae8a7f09c99e31c7042b7d4d595f03b2b1 (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding 61c761fc21e00e45c33c2bb596be442d92fb8792 (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding 14f56e9c0b8fdc2e178acdbec9781e90ef46f7e9 (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding abdc57c7ebabaaf0b622178a6a85834e1e54ff80 (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding f334e79a11e084713e82402b1a7a0e321526992a (affected)
  • d56d938b4bef3e1421a42023cdcd6e13c1f50831 up to but excluding 22e643e61b9b6299b42ff7d88bab48bccada8a5d (affected)
LinuxLinux
  • Default status: affected
  • 5.12 (affected)
  • 0 up to but excluding 5.12 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.60 up to and including 6.18.* (unaffected)
  • 7.2.14 up to and including 7.2.* (unaffected)
  • 7.3.2 up to and including 7.3.* (unaffected)
  • 7.4-rc1 up to and including * (unaffected)

Timeline

  1. 3 Nov 2026 Published

References