CVE-2026-99254 json
io_uring: don't flood a cancelling task with task_work
published 2026-11-03 5 d ago modified 2026-11-06 2 d ago also EUVD-2026-115765
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
io_uring: don't flood a cancelling task with task_work
io_ring_exit_work() asks each task which has used the ring to remove its tctx node, by task_work, and repeats that until the list is empty. io_tctx_exit_cb() doesn't touch the node while the task is in io_uring_cancel_generic(), which removes all the nodes at its end. So the work item queues the callback again as soon as it has completed, for nothing.
That is more than a waste of time. task_work_run() only returns when it finds the list empty. If the rings are released from inside the cancellation, because requests of other rings held the last references to their files, up to 64 work items keep sending callbacks to the one task which is running them. It never finds the list empty, never gets back to the cancellation, the nodes stay, and so it goes on: a task with 60 pairs of rings which poll each other ran 280000 callbacks in 5 seconds, 20 seconds after exit_group(). It ends when all the senders happen to be late at the same time. Until then the task keeps a CPU and the work items busy.
An exiting task can't be killed meanwhile. execve() cancels the requests in the same way, so a live task can get stuck there as well, for minutes. If it takes more than five, the work items run into the WARN_ON_ONCE(time_after(jiffies, timeout)) of io_ring_exit_work(). No privilege is needed for any of this.
If the callback has met a task in cancellation, wait a little before it is sent again. Nobody has to wake the work item up for that: either the node is gone by then, or it is the turn of the next round.
Patch / fix
- Linux Linux 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.2, 7.4-rc1
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.14-1
debian advisories DEBIAN-CVE-2026-99254
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112610
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/a22fb44e988b01b82235ea07f0bf0fc73e256596 commit
- git.kernel.org/stable/c/2c75ebae8a7f09c99e31c7042b7d4d595f03b2b1 commit
- git.kernel.org/stable/c/61c761fc21e00e45c33c2bb596be442d92fb8792 commit
- git.kernel.org/stable/c/14f56e9c0b8fdc2e178acdbec9781e90ef46f7e9 commit
- git.kernel.org/stable/c/abdc57c7ebabaaf0b622178a6a85834e1e54ff80 commit
- git.kernel.org/stable/c/f334e79a11e084713e82402b1a7a0e321526992a commit
- git.kernel.org/stable/c/22e643e61b9b6299b42ff7d88bab48bccada8a5d commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99254 updated cvss 3.3
kernel: kernel: Denial of Service via task_work flood during cancellation in io_uring
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9, openshift/ose-rhel-coreos-10affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/a22fb44e988b01b82235ea07f0bf0fc73e256596
- git.kernel.org /stable/c/2c75ebae8a7f09c99e31c7042b7d4d595f03b2b1
- git.kernel.org /stable/c/61c761fc21e00e45c33c2bb596be442d92fb8792
- git.kernel.org /stable/c/14f56e9c0b8fdc2e178acdbec9781e90ef46f7e9
- git.kernel.org /stable/c/abdc57c7ebabaaf0b622178a6a85834e1e54ff80
- git.kernel.org /stable/c/f334e79a11e084713e82402b1a7a0e321526992a
- git.kernel.org /stable/c/22e643e61b9b6299b42ff7d88bab48bccada8a5d
Sources
- CVE List CVE-2026-99254
- NVD CVE-2026-99254
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.