CVE-2026-99264: Linux kernel · io_uring/net: don't retry recv on uncommitted buffers
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fc8506eea4498ecba26ef8bf6dbbd74af3dc891d : patch Linux kernel soon.
Data as of 3 Nov 2026, 12:13 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fc8506eea4498ecba26ef8bf6dbbd74af3dc891d, 97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0, 21cb1770a56a51266ab96d4ed2a3b6979db59694 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in Linux kernel versions 6.7, 6.12.115, 6.16, and 6.17 and later. Users should upgrade to these or later kernel versions to remediate the issue. No additional mitigation is required as the fix addresses the root cause by properly committing partial buffers and adjusting receive semantics.
Description
A vulnerability in the Linux kernel's io_uring/net subsystem causes improper handling of partial receive buffers during retries. The kernel may retry receiving data on buffers that have not been fully committed, leading to potential data overwrites and inconsistencies. The fix changes the behavior to complete the request with the data received so far instead of retrying, disabling MSG_WAITALL for incremental or multi-buffer receives.