CVE-2026-99130: io_uring/cancel: don't spin on local work the task can't run
Vulnerability summary
CVE-2026-99130 is a medium (CVSS 6.8) vulnerability in linux. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 6.3% of scored vulnerabilities.
Not severe (CVSS 6.8, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 5 · Related 2Timeline
- 28-10-2026PublishedVulnerability first disclosed.
- 30-10-2026Last modifiedVulnerability information updated.
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.
CVSS metrics
1 score · 1 source · 1 versionEPSS trend
Probability
0.17%
Chance of exploitation in the next 30 days
Percentile
6%
Versus all other CVEs
30-day change
Change unavailable
Change unavailable
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu169 products
- linuxAll versions (No fix recorded) | < 6.8.0-151.151 | < 7.3.0-10.10 | < 7.0.0-44.44
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 6.8.0-1070.76 | < 7.3.0-1004.4 | < 7.0.0-1018.19
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Debian2 products
- linuxAll versions (No fix recorded) | < 6.12.115-2 | < 7.2.13-1
- linux-6.12< 6.12.115-2~deb12u1
Linux1 product
- linux≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 64e196a6d7173667a2a0fe2f191bc64eecd07778 | ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 8a241d7ca23be2695a1fbe587ee12eae061c31af | ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 94d13387b96e50a4288f7bbdfe401189246a11a1 | ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa | ≥ 360cd42c4e95ff06d8d7b0a54e42236c7e7c187f, < fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7 | 6.4
3 vendors · 172 products