CVE-2026-99262

published 3 Nov 2026 · updated 9 Nov 2026

io_uring/timeout: don't lose a cancel as io-wq arms a timeout

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f9d5e02649587885852f46b6dc7c081b87f0ac3a, Kernel 68cd06ba918d9658c36c1973a0184795738dcc46, Kernel 89f193dc3ef462059387e9691bf6af4b1808379a and 8 more.

In the Linux kernel, the following vulnerability has been resolved: io_uring/timeout: don't lose a cancel as io-wq arms a timeout An IORING_OP_TIMEOUT run by io-wq, because of IOSQE_ASYNC, has the same problem as poll, futex and waitid. io_wq_submit_work() looks at IO_WQ_WORK_CANCEL once, before it issues the request. A cancel in between flags the work, gets -EALREADY, and searches ->timeout_list in vain, while the worker then adds the request and starts the timer: io-wq worker io_try_cancel() io_wq_submit_work() IO_WQ_WORK_CANCEL isn't set io_async_cancel_one() sets IO_WQ_WORK_CANCEL = -EALREADY io_timeout_cancel() = -ENOENT io_timeout() adds the request to ->timeout_list hrtimer_start() = IOU_ISSUE_SKIP_COMPLETE Nobody looks at the flag again, and the timeout runs its course. At ring exit, io_uring_try_cancel_requests() cancels io-wq work and then kills the timeouts the same way, so an exiting task can get stuck for the full duration of such a timeout. Look at the flag under ->timeout_lock, which the search takes as well, and fail the request if it is set. If the search came first, the flag is visible. If it comes later, it finds the request on the list.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <f9d5e02649587885852f46b6dc7c081b87f0ac3a, >=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <68cd06ba918d9658c36c1973a0184795738dcc46, >=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <89f193dc3ef462059387e9691bf6af4b1808379a, >=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <df705a274da10da7bb546e08b49fa80a6ef19c78, >=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <f10ab47077e63d6eee35b242c257c3947bb49e64, >=ce35a47a3a0208a77b4d31b7f2e8ed57d624093d <f1fabf17f37b252b11d8fe5c70c8056b70b005ca, =5.6f9d5e02649587885852f46b6dc7c081b87f0ac3a, 68cd06ba918d9658c36c1973a0184795738dcc46, 89f193dc3ef462059387e9691bf6af4b1808379a, df705a274da10da7bb546e08b49fa80a6ef19c78, f10ab47077e63d6eee35b242c257c3947bb49e64, f1fabf17f37b252b11d8fe5c70c8056b70b005ca
linux-kernel: Kernel>=6.13.0 <6.18.60, >=6.19.0 <7.2.14, >=6.2.0 <6.6.161, >=6.7.0 <6.12.115, >=5.6.0 <6.1.1916.18.60, 7.2.14, 6.6.161, 6.12.115, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99262 severity on Zeptric[![CVE-2026-99262](https://zeptric.io/badge/cve/CVE-2026-99262.svg)](https://zeptric.io/cve/CVE-2026-99262)