CVE-2025-21927: Linux kernel · nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 30 Oct 2026, 16:33 UTC
Contested
Scorers differ by 2 or more points| CNA (Linux) | CVSS 3.1 | 9.8 |
|---|---|---|
| CISA-ADP | CVSS 3.1 | 7.8 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
Description
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() nvme_tcp_recv_pdu() doesn't check the validity of the header length. When header digests are enabled, a target might send a packet with an invalid header length (e.g. 255), causing nvme_tcp_verify_hdgst() to access memory outside the allocated area and cause memory corruptions by overwriting it with the calculated digest. Fix this by rejecting packets with an unexpected header length.
References
- nvd.nist.gov/vuln/detail/CVE-2025-21927 (opens in a new tab)
- git.kernel.org/stable/c/22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126 (opens in a new tab)
- git.kernel.org/stable/c/3b54109b2f771f74fd53b027429796326f84ab36 (opens in a new tab)
- git.kernel.org/stable/c/9d22cf5cc94cd7dee84773ec41db78a46107dfa3 (opens in a new tab)
- git.kernel.org/stable/c/9fbc953d6b38bc824392e01850f0aeee3b348722 (opens in a new tab)
- git.kernel.org/stable/c/ad95bab0cd28ed77c2c0d0b6e76e03e031391064 (opens in a new tab)