CVE-2026-99264

published 3 Nov 2026 · updated 17 Nov 2026

io_uring/net: don't retry recv on uncommitted buffers

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8444de681a179e41a4eb92d5bbe770a0677074a6, Kernel 97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0, Kernel fc8506eea4498ecba26ef8bf6dbbd74af3dc891d and 5 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=21a4ddb0f5e933f372808c10b9ac704505751bb1, =2eb7937b5fc7fcd90eab7bebb0181214b61b9283, =3b53dc1c641f2884d4750fc25aaf6c36b90db606, =6.17, >=41b70df5b38bc80967d2e0ed55cc3c3896bba781 <8444de681a179e41a4eb92d5bbe770a0677074a6, >=41b70df5b38bc80967d2e0ed55cc3c3896bba781 <97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0, >=41b70df5b38bc80967d2e0ed55cc3c3896bba781 <fc8506eea4498ecba26ef8bf6dbbd74af3dc891d, >=6.12.44 <6.12.115, >=6.15.11 <6.16, >=6.16.2 <6.17, >=6.6.103 <6.7, >=fe9da1812f8697a38f7e30991d568ec199e16059 <21cb1770a56a51266ab96d4ed2a3b6979db596948444de681a179e41a4eb92d5bbe770a0677074a6, 97b8dc36ba3cb176b74a7929140aeaeb40d5cdc0, fc8506eea4498ecba26ef8bf6dbbd74af3dc891d, 6.12.115, 6.16, 6.17, 6.7, 21cb1770a56a51266ab96d4ed2a3b6979db59694

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99264 severity on Zeptric[![CVE-2026-99264](https://zeptric.io/badge/cve/CVE-2026-99264.svg)](https://zeptric.io/cve/CVE-2026-99264)