CVE-2026-99130

io_uring/cancel: don't spin on local work the task can't run

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/cancel: don't spin on local work the task can't run io_uring_cancel_generic() refuses to sleep while any ring on the exiting task's tctx has local work pending. It assumes the task is that ring's submitter and that the next io_uring_try_cancel_requests() pass will run the work. This does not hold for a ring that was still IORING_SETUP_R_DISABLED when the task got its tctx node from io_uring_create() or io_ringfd_register(). The submitter is set later by IORING_REGISTER_ENABLE_RINGS, possibly from another task, and only the submitter may run local work on an IORING_SETUP_DEFER_TASKRUN ring. To the exiting task the work stays pending forever, the loop never reaches schedule(), and the task trips the WARN_ON_ONCE() once and then spins in do_exit(). An unprivileged user can set this up at will by creating a disabled ring, having a child enable it and stop, posting to the ring with IORING_OP_MSG_RING and exiting with a request in flight that only the child can complete. The exiting thread burns a CPU until the child runs or dies, and with panic_on_warn set the WARN panics the kernel. Fix by skipping the sleep only when io_allowed_defer_tw_run() allows the task to run the work. This is reasonable since work it cannot run cannot complete any of its requests either, so nothing is lost by sleeping. Drop the WARN_ON_ONCE() since handing a disabled ring to another thread is a supported scenario, not a bug state.

Key facts

Published
28 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.25% 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
  • 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f up to but excluding 64e196a6d7173667a2a0fe2f191bc64eecd07778 (affected)
  • 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f up to but excluding 8a241d7ca23be2695a1fbe587ee12eae061c31af (affected)
  • 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f up to but excluding 94d13387b96e50a4288f7bbdfe401189246a11a1 (affected)
  • 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f up to but excluding 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa (affected)
  • 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f up to but excluding fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7 (affected)
LinuxLinux
  • Default status: affected
  • 6.4 (affected)
  • 0 up to but excluding 6.4 (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References