Answer in brief
CVE-2025-21927 records a Unknown severity vulnerability in nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <9fbc953d6b38bc824392e01850f0aeee3b348722 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <ad95bab0cd28ed77c2c0d0b6e76e03e031391064 | 9fbc953d6b38bc824392e01850f0aeee3b348722, 22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126, ad95bab0cd28ed77c2c0d0b6e76e03e031391064 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Apr 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21927 records a Unknown severity vulnerability in nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <9fbc953d6b38bc824392e01850f0aeee3b348722 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <ad95bab0cd28ed77c2c0d0b6e76e03e031391064 | 9fbc953d6b38bc824392e01850f0aeee3b348722, 22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126, ad95bab0cd28ed77c2c0d0b6e76e03e031391064 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Apr 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.