CVE-2025-38730

io_uring/net: commit partial buffers on retry

State
Published
Severity
7.8 High
Published
Sep 4, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 to before 3b53dc1c641f2884d4750fc25aaf6c36b90db606Affected
  • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 to before fe9da1812f8697a38f7e30991d568ec199e16059Affected
  • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 to before 21a4ddb0f5e933f372808c10b9ac704505751bb1Affected
  • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 to before 2eb7937b5fc7fcd90eab7bebb0181214b61b9283Affected
  • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 to before 41b70df5b38bc80967d2e0ed55cc3c3896bba781Affected
LinuxLinux
  • 6.4Affected
  • before 6.4Not affected
  • 6.6.103 through 6.6.*Not affected
  • 6.12.44 through 6.12.*Not affected
  • 6.15.11 through 6.15.*Not affected
  • 6.16.2 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.