CVE-2025-38405 is a memory leak vulnerability in the Linux kernel NVMe target (nvmet) subsystem. When nvmet processes commands that include metadata, it initializes inline bios with bio_init but fails to perform the corresponding bio_uninit during teardown. After the block-layer change introduced by commit bf4c89fc8797, callers using bio_init must explicitly invoke bio_uninit to release associated bio integrity allocations. Because nvmet omitted that cleanup step, the bio integrity structure associated with bio->bi_integrity remains allocated, causing a continuous leak of kernel memory from the kmalloc-128 slab or related allocations. The issue is resolved by uninitializing the inline bio so integrity-related memory is fully deallocated.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.