io_uring/net: don't retry recv on uncommitted buffers
Summary
| CVE | CVE-2026-99264 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-03 12:17:33 UTC |
| Updated | 2026-11-03 12:17:33 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected fe9da1812f8697a38f7e30991d568ec199e16059 21cb1770a56a51266ab96d4ed2a3b6979db59694 git |
Not specified |
| CNA |
Linux |
Linux |
affected 41b70df5b38bc80967d2e0ed55cc3c3896bba781 fc8506eea4498ecba26ef8bf6dbbd74af3dc891d git |
Not specified |
| CNA |
Linux |
Linux |
affected 41b70df5b38bc80967d2e0ed55cc3c3896bba781 97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3b53dc1c641f2884d4750fc25aaf6c36b90db606 git |
Not specified |
| CNA |
Linux |
Linux |
affected 21a4ddb0f5e933f372808c10b9ac704505751bb1 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2eb7937b5fc7fcd90eab7bebb0181214b61b9283 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.12.44 6.12.115 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6.103 6.7 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.15.11 6.16 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.16.2 6.17 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.17 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.17 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.115 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.60 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.14 7.2.* semver |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/21cb1770a56a51266ab96d4ed2a3b6979db59694 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/fc8506eea4498ecba26ef8bf6dbbd74af3dc891d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.