cve.bz

CVE-2026-99229 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: io_uring/wait: don't spin on a stuck overflow list As long as IO_CHECK_CQ_OVERFLOW_BIT is set, io_cqring_wait_schedule() returns right away, before it gets to look at signals or arms the timeout, for io_cqring_wait() to flush the overflow list. If that doesn't empty the list, and the CQ ring doesn't hold the number of events the caller wants, the loop starts over, with the same result. The task spins in the kernel, and can't be killed. The assumption is that this can't happen: if CQEs can't be flushed, the ring is full, and min_events is capped to the size of the ring. But: - With IORING_SETUP_CQE_MIXED a 32b CQE needs two contiguous entries. It is stuck on the list if a single one is free, and then the ring holds less than cq_entries events. A single threaded application that asks for as many events as the ring has entries never gets out of io_uring_enter(). - Whether the ring is full is up to the CQ head, which the application can write to. While one thread waits for events on an empty ring, another one can move the head back so that the ring looks full and have a CQE overflow. The waiter can't be stopped any more, not even by SIGKILL. Only the application can make room in the CQ ring. Return to it if the list could not be flushed.
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.60
  • Linux Linux: fixed in 7.2.14
  • Linux Linux: fixed in 7.3.2
  • Linux Linux: fixed in 7.4-rc1
  • Debian, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99229 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99229?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99229?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99229 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-99229

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99229](https://cve.bz/cve/badge/CVE-2026-99229.svg)](https://cve.bz/cve/CVE-2026-99229)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99229"><img src="https://cve.bz/cve/badge/CVE-2026-99229.svg" alt="CVE-2026-99229"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.3 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.60
Linux7.27.2.14
Linux7.37.3.2
Linuxlater releases7.4-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99229
Debian13linux6.12.115-1DEBIAN-CVE-2026-99229
Debian14linux7.2.14-1DEBIAN-CVE-2026-99229
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99229
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99229
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99229
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-99229
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99229
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99229
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99229
UbuntuNvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99229
UbuntuPro:FIPS-updates:24.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99229
UbuntuPro:Realtime:22.04:LTSlinux-realtime-6.8no fix listedUBUNTU-CVE-2026-99229
UbuntuPro:Realtime:24.04:LTSlinux-realtime, linux-realtime-6.14, linux-realtime-6.17 and 1 moreno fix listedUBUNTU-CVE-2026-99229
openSUSETumbleweedkernel-source7.3.3-1.1openSUSE-SU-2026:12497-1
Azure Linux3kernel6.6.161.1-1AZL-112562
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99229
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99229

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate rather than Important because exploitation requires local access and can only result in a denial of service condition without compromising data confidentiality or system integrity. An authenticated local user must be able to interact with the kernel's asynchronous I/O framework and create specialized completion queue configurations to trigger the hang. In enterprise installations where io_uring is restricted or not utilized by unprivileged accounts, exposure is significantly reduced. Because the spin condition prevents the affected task from receiving termination signals, the impact is confined to CPU consumption by the stuck process unless system resources become exhausted.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-10Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99229.

References

Check your stackJSON