CVE-2025-38730
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| โ | Affected | โ |
AlmaLinux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | kernel-64k-devel-5.14.0-611.30.1.el9_7.aarch64.rpm |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.48-1 |
| sid | Fixed | 6.16.3-1 |
| forky | Fixed | 6.16.3-1 |
| bullseye | Fixed | 0 |
| bookworm | Fixed | 0 |
Red Hat Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | โ |
Rocky Linux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | โ |
References
- https://access.redhat.com/errata/RHSA-2026:2212
- https://www.suse.com/security/cve/CVE-2025-38730.html
- https://errata.rockylinux.org/RLSA-2026:2212
- https://security-tracker.debian.org/tracker/CVE-2025-38730
- https://bugzilla.redhat.com/2363315
- https://bugzilla.redhat.com/2365032
- https://bugzilla.redhat.com/2373326
- https://bugzilla.redhat.com/2373354
- https://bugzilla.redhat.com/2383404
- https://bugzilla.redhat.com/2383421
- https://bugzilla.redhat.com/2383487
- https://bugzilla.redhat.com/2393191
- https://bugzilla.redhat.com/2394601
- https://bugzilla.redhat.com/2414506
- https://bugzilla.redhat.com/2414521
- https://bugzilla.redhat.com/2414522
- https://bugzilla.redhat.com/2414523
- https://bugzilla.redhat.com/2419837
- https://bugzilla.redhat.com/2419919
- https://bugzilla.redhat.com/2419920
- https://errata.almalinux.org/9/ALSA-2026-2212.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.