SECUFOCUSNOW
Home›CVE index›CVE-2025-21927
Review reviewHigh

CVE-2025-21927

Linux Linux, linux kernel

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.

CVSS
7.8
EPSS
0.46%
37.7% percentile
CISA KEV
Not listed
Published
2025.04.02
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.46%
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 3f2304f8c6d6ed97849057bd16fee99e434ca796 < 9fbc953d6b38bc824392e01850f0aeee3b348722, >= 3f2304f8c6d6ed97849057bd16fee99e434ca796 < 22b06c89aa6b2d1ecb8aea72edfb9d53af8d5126, >= 3f2304f8c6d6ed97849057bd16fee99e434ca796 < ad95bab0cd28ed77c2c0d0b6e76e03e031391064, >= 5.0, >= 5.0 < 6.12.19, >= 6.13 < 6.13.7, 6.14
Fixed versions
6.12.19, 6.13.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787