CVE-2026-99229: io_uring/wait: don't spin on a stuck overflow list
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Fixed version: Linux Linux 34f5a664c34d3cb62f6bec7f4156754594a7d25b, 4a89352edd8b3e20d1e1fb33f0fc297dd137149f, a6cfc85c6bf9498aaf1978b503f9663635a1aa22.
Low priority for now. Upgrade to Linux Linux 34f5a664c34d3cb62f6bec7f4156754594a7d25b, 4a89352edd8b3e20d1e1fb33f0fc297dd137149f, a6cfc85c6bf9498aaf1978b503f9663635a1aa22 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 2, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.3affected
- 3fcf19d592d5cb63eb209400b22055651e3c27d0 and later · before bf1d2ed84b3162e3b0e0bb7018ac59147da6e975affected · git
- 3fcf19d592d5cb63eb209400b22055651e3c27d0 and later · before a6cfc85c6bf9498aaf1978b503f9663635a1aa22affected · git
- 3fcf19d592d5cb63eb209400b22055651e3c27d0 and later · before 4a89352edd8b3e20d1e1fb33f0fc297dd137149faffected · git
- 3fcf19d592d5cb63eb209400b22055651e3c27d0 and later · before c347691e5dc5481b2d6943c123619e04847fb0dcaffected · git
- 3fcf19d592d5cb63eb209400b22055651e3c27d0 and later · before 34f5a664c34d3cb62f6bec7f4156754594a7d25baffected · git
- before 6.3not affected · semver
- 6.6.161 and later · up to and including 6.6.*not affected · semver
- 6.12.115 and later · up to and including 6.12.*not affected · semver
- 6.18.60 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.115-1 | 6.12.115-1 |
| Debian:14 | linux | from 0 | — |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99227Nov 2, 2026 · io_uring/waitid: prevent cancel reference wrap31Monitor
- ← EarlierCVE-2026-99228Nov 2, 2026 · io_uring/io-wq: don't lose the signal that ends work0Monitor
- Later →CVE-2026-99230Nov 2, 2026 · io_uring/cmd: don't leave list poison in ->hash_node0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 34f5a664c34d3cb62f6bec7f4156754594a7d25b | Vendor (CNA) |
| Linux Linux | 4a89352edd8b3e20d1e1fb33f0fc297dd137149f | Vendor (CNA) |
| Linux Linux | a6cfc85c6bf9498aaf1978b503f9663635a1aa22 | Vendor (CNA) |
| Linux Linux | bf1d2ed84b3162e3b0e0bb7018ac59147da6e975 | Vendor (CNA) |
| Linux Linux | c347691e5dc5481b2d6943c123619e04847fb0dc | Vendor (CNA) |
| debian:linux | 6.12.115-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 5, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.