{"id":"CVE-2026-99130","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:\n\nio_uring/cancel: don't spin on local work the task can't run\n\nio_uring_cancel_generic() refuses to sleep while any ring on the exiting\ntask's tctx has local work pending. It assumes the task is that ring's\nsubmitter and that the next io_uring_try_cancel_requests() pass will run\nthe work. This does not hold for a ring that was still\nIORING_SETUP_R_DISABLED when the task got its tctx node from\nio_uring_create() or io_ringfd_register(). The submitter is set later by\nIORING_REGISTER_ENABLE_RINGS, possibly from another task, and only the\nsubmitter may run local work on an IORING_SETUP_DEFER_TASKRUN ring. To\nthe exiting task the work stays pending forever, the loop never reaches\nschedule(), and the task trips the WARN_ON_ONCE() once and then spins in\ndo_exit().\n\nAn unprivileged user can set this up at will by creating a disabled\nring, having a child enable it and stop, posting to the ring with\nIORING_OP_MSG_RING and exiting with a request in flight that only the\nchild can complete. The exiting thread burns a CPU until the child runs\nor dies, and with panic_on_warn set the WARN panics the kernel.\n\nFix by skipping the sleep only when io_allowed_defer_tw_run() allows the\ntask to run the work. This is reasonable since work it cannot run cannot\ncomplete any of its requests either, so nothing is lost by sleeping.\nDrop the WARN_ON_ONCE() since handing a disabled ring to another thread\nis a supported scenario, not a bug state.","modified":"2026-11-01T02:30:54.612296674Z","published":"2026-10-28T10:34:43.514Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99130.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/3005459e0ddfcef0f555b6e81f672f2c49a1c0aa"},{"type":"WEB","url":"https://git.kernel.org/stable/c/64e196a6d7173667a2a0fe2f191bc64eecd07778"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8a241d7ca23be2695a1fbe587ee12eae061c31af"},{"type":"WEB","url":"https://git.kernel.org/stable/c/94d13387b96e50a4288f7bbdfe401189246a11a1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99130.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99130"},{"type":"PACKAGE","url":"https://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"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"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"}}],"schema_version":"1.9.2"}