CVE-2025-38405: nvmet: fix memory leak of bio integrity
In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix memory leak of bio integrity
If nvmet receives commands with metadata there is a continuous memory
leak of kmalloc-128 slab or more precisely bio->bi_integrity.
Since commit bf4c89fc8797 ("block: don't call bio_uninit from bio_endio")
each user of bio_init has to use bio_uninit as well. Otherwise the bio
integrity is not getting free. Nvmet uses bio_init for inline bios.
Uninit the inline bio to complete deallocation of integrity in bio.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux NVMe target can continuously leak kernel memory when processing commands containing metadata. Sustained leakage could exhaust resources, destabilize the host, or interrupt storage services. The issue affects availability; the supplied CVSS assessment does not indicate data theft or modification.
Executive priority
Prioritize reachable nvmet storage hosts because repeated metadata processing may cause resource exhaustion and service interruption. Patch through the normal kernel maintenance process, accelerating systems exposed to untrusted initiators. The absence of cited active exploitation reduces incident-response urgency but does not remove availability risk.
Technical view
The nvmet inline-bio path calls bio_init but failed to call bio_uninit. Following Linux commit bf4c89fc8797, that omission leaves bio->bi_integrity allocations, including kmalloc-128 slab objects, unreleased. The cited stable changes correct the lifecycle by uninitializing the inline bio, allowing integrity metadata to be freed.
Likely exposure
Exposure is limited to Linux systems operating as NVMe targets through nvmet and receiving metadata-bearing commands. The supplied version entries are ambiguous and should not be treated as complete ranges. Confirm whether each distribution kernel includes a cited fix or backport.
Exploitation context
The bundle reports CVSS 7.5 with network reachability, low complexity, no required privileges, and high availability impact. It marks the CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. This does not prove exploitation is impossible.
Researcher notes
This is a kernel resource-lifetime defect in the nvmet inline-bio path. The retained object is bio integrity metadata, and the stated correction adds the missing bio_uninit operation. No CWE is assigned. The bundle does not provide complete affected-range semantics, reproduction evidence, crash thresholds, or exploitation telemetry.
Mitigation direction
Apply a vendor kernel containing a cited stable fix after appropriate testing.
Check distribution advisories and package changelogs for backported fixes.
Until patched, restrict NVMe target access to trusted initiators through existing network controls.
Disable nvmet on systems where NVMe target functionality is unnecessary.
Validation and detection
Inventory kernel versions and identify hosts configured as nvmet targets.
Verify the installed kernel contains a cited fix or documented vendor backport.
Confirm whether untrusted initiators can reach exposed NVMe target services.
Monitor kernel memory and slab usage for sustained growth during legitimate metadata workloads.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38405 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.