Loading vulnerability…
CVE-2025-21927 is an out-of-bounds write vulnerability in the Linux kernel NVMe over TCP implementation. The nvme_tcp_recv_pdu() receive path failed to validate a received protocol data unit header length. When NVMe/TCP header digests are enabled, an NVMe/TCP target can send a PDU with an unexpected header length, causing nvme_tcp_verify_hdgst() to operate beyond the allocated buffer and overwrite adjacent memory with the computed digest. The upstream correction rejects PDUs whose header length is not expected.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A potential memory-corruption vulnerability in the Linux kernel NVMe over TCP receive-PDU processing function, nvme_tcp_recv_pdu().
A potential memory-corruption vulnerability in the Linux kernel NVMe-over-TCP nvme_tcp_recv_pdu() function, fixed by the Red Hat Enterprise Linux 9 kernel update.
A vulnerability included in the OpenShift Container Platform 4.12.76 security advisory; no technical description is provided in the content.
Unknown
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.