CVE-2026-99130

Source
https://cve.org/CVERecord?id=CVE-2026-99130
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99130.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99130
Downstream
Published
2026-10-28T10:34:43Z
Modified
2026-11-01T02:30:54Z
Summary
io_uring/cancel: don't spin on local work the task can't run
Details

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.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99130.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
360cd42c4e95ff06d8d7b0a54e42236c7e7c187f
Fixed
64e196a6d7173667a2a0fe2f191bc64eecd07778
Fixed
8a241d7ca23be2695a1fbe587ee12eae061c31af
Fixed
94d13387b96e50a4288f7bbdfe401189246a11a1
Fixed
3005459e0ddfcef0f555b6e81f672f2c49a1c0aa
Fixed
fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99130.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.4.0
Fixed
6.6.161
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.115
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.59
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.2.13

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99130.json"