Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2025-21927

This vulnerability allows an attacker to corrupt memory in the Linux kernel’s NVMe over TCP implementation by sending a packet with an invalid header length. The flaw can lead to arbitrary code execution or denial of service and has been fixed in recent kernel releases.

publishedApr 1, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
37th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 29, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel, especially versions 6.14 and earlier that do not contain the patch. Typical users are system administrators and organizations running Linux servers.

02

Real-world impact

An attacker could send crafted NVMe over TCP packets to a vulnerable system, causing memory corruption that could lead to arbitrary code execution, privilege escalation, or crashing the system.

03

Why this severity

The CVSS score of 9.8 reflects the vulnerability’s high impact on confidentiality, integrity, and availability, and the fact that it can be exploited remotely without authentication or user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Check the current kernel version on the system.
  2. 02Update the kernel to the latest stable release that includes the nvme-tcp patch (e.g., 6.14 or newer).
  3. 03Reboot the system to load the updated kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Apr 1, 2025 · Apr 1, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 7d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 6d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →