Answer in brief
CVE-2025-38730 records a Unknown severity vulnerability in io_uring/net: commit partial buffers on retry. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <3b53dc1c641f2884d4750fc25aaf6c36b90db606 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <fe9da1812f8697a38f7e30991d568ec199e16059 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <21a4ddb0f5e933f372808c10b9ac704505751bb1 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <2eb7937b5fc7fcd90eab7bebb0181214b61b9283 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <41b70df5b38bc80967d2e0ed55cc3c3896bba781 | 3b53dc1c641f2884d4750fc25aaf6c36b90db606, fe9da1812f8697a38f7e30991d568ec199e16059, 21a4ddb0f5e933f372808c10b9ac704505751bb1, 2eb7937b5fc7fcd90eab7bebb0181214b61b9283, 41b70df5b38bc80967d2e0ed55cc3c3896bba781 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: commit partial buffers on retry Ring provided buffers are potentially only valid within the single execution context in which they were acquired. io_uring deals with this and invalidates them on retry. But on the networking side, if MSG_WAITALL is set, or if the socket is of the streaming type and too little was processed, then it will hang on to the buffer rather than recycle or commit it. This is problematic for two reasons: 1) If someone unregisters the provided buffer ring before a later retry, then the req->buf_list will no longer be valid. 2) If multiple sockers are using the same buffer group, then multiple receives can consume the same memory. This can cause data corruption in the application, as either receive could land in the same userspace buffer. Fix this by disallowing partial retries from pinning a provided buffer across multiple executions, if ring provided buffers are used.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38730 records a Unknown severity vulnerability in io_uring/net: commit partial buffers on retry. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <3b53dc1c641f2884d4750fc25aaf6c36b90db606 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <fe9da1812f8697a38f7e30991d568ec199e16059 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <21a4ddb0f5e933f372808c10b9ac704505751bb1 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <2eb7937b5fc7fcd90eab7bebb0181214b61b9283 || >=c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 <41b70df5b38bc80967d2e0ed55cc3c3896bba781 | 3b53dc1c641f2884d4750fc25aaf6c36b90db606, fe9da1812f8697a38f7e30991d568ec199e16059, 21a4ddb0f5e933f372808c10b9ac704505751bb1, 2eb7937b5fc7fcd90eab7bebb0181214b61b9283, 41b70df5b38bc80967d2e0ed55cc3c3896bba781 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: commit partial buffers on retry Ring provided buffers are potentially only valid within the single execution context in which they were acquired. io_uring deals with this and invalidates them on retry. But on the networking side, if MSG_WAITALL is set, or if the socket is of the streaming type and too little was processed, then it will hang on to the buffer rather than recycle or commit it. This is problematic for two reasons: 1) If someone unregisters the provided buffer ring before a later retry, then the req->buf_list will no longer be valid. 2) If multiple sockers are using the same buffer group, then multiple receives can consume the same memory. This can cause data corruption in the application, as either receive could land in the same userspace buffer. Fix this by disallowing partial retries from pinning a provided buffer across multiple executions, if ring provided buffers are used.
Quoted source text, attributed separately from HOL analysis.