Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38730: io_uring/net: commit partial buffers on retry

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 21a4ddb0f5e933f372808c10b9ac704505751bb1, 2eb7937b5fc7fcd90eab7bebb0181214b61b9283, 3b53dc1c641f2884d4750fc25aaf6c36b90db606; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.

Low priority for now. Upgrade to Linux Linux 21a4ddb0f5e933f372808c10b9ac704505751bb1, 2eb7937b5fc7fcd90eab7bebb0181214b61b9283, 3b53dc1c641f2884d4750fc25aaf6c36b90db606; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 4, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38730

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.4 and later · before 6.6.103
  • linux linux kernel6.7 and later · before 6.12.44
  • linux linux kernel6.13 and later · before 6.15.11
  • linux linux kernel6.16 and later · before 6.16.2
  • linux linux kernel6.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 and later · before 3b53dc1c641f2884d4750fc25aaf6c36b90db606affected · git
    • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 and later · before fe9da1812f8697a38f7e30991d568ec199e16059affected · git
    • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 and later · before 21a4ddb0f5e933f372808c10b9ac704505751bb1affected · git
    • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 and later · before 2eb7937b5fc7fcd90eab7bebb0181214b61b9283affected · git
    • c56e022c0a27142b7b59ae6bdf45f86bf4b298a1 and later · before 41b70df5b38bc80967d2e0ed55cc3c3896bba781affected · git
    • before 6.4not affected · semver
    • 6.6.103 and later · up to and including 6.6.*not affected · semver
    • 6.12.44 and later · up to and including 6.12.*not affected · semver
    • 6.15.11 and later · up to and including 6.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.35.1.el10_16.12.0-124.35.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.35.1.el10_16.12.0-124.35.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38728Sep 4, 2025 · smb3: fix for slab out of bounds on mount to ksmbd
    28Monitor
  • ← EarlierCVE-2025-38729Sep 4, 2025 · ALSA: usb-audio: Validate UAC3 power domain descriptors, too
    31Monitor
  • Later →CVE-2025-38731Sep 5, 2025 · drm/xe: Fix vm_bind_ioctl double free bug
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux21a4ddb0f5e933f372808c10b9ac704505751bb1Vendor (CNA)
Linux Linux2eb7937b5fc7fcd90eab7bebb0181214b61b9283Vendor (CNA)
Linux Linux3b53dc1c641f2884d4750fc25aaf6c36b90db606Vendor (CNA)
Linux Linux41b70df5b38bc80967d2e0ed55cc3c3896bba781Vendor (CNA)
Linux Linuxfe9da1812f8697a38f7e30991d568ec199e16059Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.48-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.30.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records