CVE-2026-99130io_uring/cancel: don't spin on local work the task can't run
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 33 days later
· 33 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f – < 64e196a6d7173667a2a0fe2f191bc64eecd07778
- affected 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f – < 8a241d7ca23be2695a1fbe587ee12eae061c31af
- affected 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f – < 94d13387b96e50a4288f7bbdfe401189246a11a1
- affected 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f – < 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa
- affected 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f – < fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/64e196a6d7173667a2a0fe2f191bc64eecd07778 (opens in a new tab)
- https://git.kernel.org/stable/c/8a241d7ca23be2695a1fbe587ee12eae061c31af (opens in a new tab)
- https://git.kernel.org/stable/c/94d13387b96e50a4288f7bbdfe401189246a11a1 (opens in a new tab)
- https://git.kernel.org/stable/c/3005459e0ddfcef0f555b6e81f672f2c49a1c0aa (opens in a new tab)
- https://git.kernel.org/stable/c/fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-111882 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99130)Record last updated .