CVE-2026-99264
Received Received - Intake

Memory Corruption in Linux Kernel io_uring

Vulnerability report for CVE-2026-99264, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't retry recv on uncommitted buffers Commit 41b70df5b38b ("io_uring/net: commit partial buffers on retry") commits ring provided buffers when a receive is going to be retried after a partial transfer, so that another request using the same buffer group can't be handed the memory the first one keeps receiving into. It commits the number of bytes received so far. That does the job for a single buffer which is consumed as a whole, but the request hangs on to all it has mapped: - For a buffer ring with IOU_PBUF_RING_INC only these bytes are consumed. The rest of the buffer stays at the head of the ring. - For a bundle only the buffers which hold these bytes are consumed, the others that were peeked stay in the ring. In both cases the next receive with that buffer group gets memory that the retried request is still going to write to, and whoever comes last overwrites the data of the other. What the retry fills isn't committed at all, as the buffer list isn't known any more at that point. So the kernel hands it out again later on, while the CQE tells the application that it was used, and for an incremental buffer that it is done with. The remainder can't be committed in advance: if the request ends up receiving less, there is no way to tell the application that more was consumed than the CQE accounts for. Complete the request with what it has got instead of retrying it. MSG_WAITALL is no longer honoured for receives into incremental buffers or multi buffer bundles, they can return a short count, with the request marked as failed like for other short MSG_WAITALL transfers.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 11 associated CPEs
Vendor Product Version / Range
Linux Linux fe9da1812f8697a38f7e30991d568ec199e16059
Linux Linux 41b70df5b38bc80967d2e0ed55cc3c3896bba781
Linux Linux 41b70df5b38bc80967d2e0ed55cc3c3896bba781
Linux Linux 3b53dc1c641f2884d4750fc25aaf6c36b90db606
Linux Linux 21a4ddb0f5e933f372808c10b9ac704505751bb1
Linux Linux 2eb7937b5fc7fcd90eab7bebb0181214b61b9283
Linux Linux 6.12.44
Linux Linux 6.6.103
Linux Linux 6.15.11
Linux Linux 6.16.2
Linux Linux 6.17

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves io_uring's network receive operations. When a receive operation is retried after a partial transfer, the kernel commits only the bytes received so far to the buffer. However, for buffer rings with incremental consumption or multi-buffer bundles, the remaining buffers stay in the ring and can be reused by subsequent operations. This leads to data corruption as new operations overwrite data still being written by the retried request.

Detection Guidance

This vulnerability is specific to the Linux kernel's io_uring subsystem and cannot be detected via standard network scanning tools. Detection requires checking the kernel version and io_uring configuration. Use uname -a to check the kernel version and grep for io_uring in /proc/modules or /proc/kallsyms.

Impact Analysis

This vulnerability can cause data corruption in network applications using io_uring for receiving data. It may lead to incorrect data being processed or stored, potentially causing crashes, security issues, or unreliable behavior in affected systems.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for this io_uring issue. Monitor kernel security advisories and apply updates promptly. Disable io_uring if not required by removing the module or using kernel parameters to restrict its use.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-99264. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...