CVE-2025-38730High· 7.8▾ TwilightIn 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_urin…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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:
If someone unregisters the provided buffer ring before a later retry, then the req->buf_list will no longer be valid.
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.
Linux >= c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 < 3b53dc1c641f2884d4750fc25aaf6c36b90db606Linux >= c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 < fe9da1812f8697a38f7e30991d568ec199e16059Linux >= c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 < 21a4ddb0f5e933f372808c10b9ac704505751bb1Linux >= c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 < 2eb7937b5fc7fcd90eab7bebb0181214b61b9283Linux >= c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 < 41b70df5b38bc80967d2e0ed55cc3c3896bba781Linux 6.4Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets