Vulnerability · Published Nov 3, 2026 · Assigned by Linux

CVE-2026-99254io_uring: don't flood a cancelling task with task_work

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-99254
Debian:13linux6.12.115-1DEBIAN-CVE-2026-99254
Debian:14linux7.2.14-1DEBIAN-CVE-2026-99254
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linuxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-awsno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-gcpno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-oracleno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-raspino fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-realtimeno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99254
Ubuntu:26.10linux-riscvno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-99254
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-99254
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-99254

Affected products (as reported)

VendorProductVersions
Linux Linux d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before a22fb44e988b01b82235ea07f0bf0fc73e256596d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before 2c75ebae8a7f09c99e31c7042b7d4d595f03b2b1d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before 61c761fc21e00e45c33c2bb596be442d92fb8792d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before 14f56e9c0b8fdc2e178acdbec9781e90ef46f7e9d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before abdc57c7ebabaaf0b622178a6a85834e1e54ff80d56d938b4bef3e1421a42023cdcd6e13c1f50831 – before 22e643e61b9b6299b42ff7d88bab48bccada8a5d
Linux Linux 5.12

References