CVE-2025-38730

io_uring/net: commit partial buffers on retry

HIGH
7.8
CVSS Score
Published: September 4, 2025 at 03:33 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.13 ≤ v < 6.15.116.16 ≤ v < 6.16.26.4 ≤ v < 6.6.1036.7 ≤ v < 6.12.446.176.17 rc1c56e022c0a27142b7b59ae6bdf45f86bf4b298a1
Vendor states this is fixed in 21a4ddb0f5e933f372808c10b9ac704505751bb1 (fixed)
Vendor states this is fixed in 2eb7937b5fc7fcd90eab7bebb0181214b61b9283 (fixed)
Vendor states this is fixed in 3b53dc1c641f2884d4750fc25aaf6c36b90db606 (fixed)
Vendor states this is fixed in 41b70df5b38bc80967d2e0ed55cc3c3896bba781 (fixed)
Vendor states this is fixed in fe9da1812f8697a38f7e30991d568ec199e16059 (fixed)
Vendor states this is fixed in 6.12.44 (unaffected)
Vendor states this is fixed in 6.15.11 (unaffected)
Vendor states this is fixed in 6.16.2 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)
Vendor states this is fixed in 6.6.103 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/21a4ddb0f5e933f372808c10b9ac704505751bb1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2eb7937b5fc7fcd90eab7bebb0181214b61b9283
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3b53dc1c641f2884d4750fc25aaf6c36b90db606
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/41b70df5b38bc80967d2e0ed55cc3c3896bba781
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fe9da1812f8697a38f7e30991d568ec199e16059

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card