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

CVE-2025-38209

A critical bug in the Linux kernel’s NVMe over TCP implementation can cause a use‑after‑free error, potentially crashing the system or allowing code execution. The flaw occurs when the second admin queue configuration fails, leaving a dangling tag set that is later accessed by a timeout handler. The issue has been fixed in a kernel patch that ensures the tag set is removed on failure.

publishedJul 4, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
23th 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 (NVMe over TCP) – any system running a kernel version before the patch that contains the bug. Typical users are Linux administrators and end‑users who rely on NVMe over TCP for storage networking.

02

Real-world impact

An attacker could trigger the bug to crash the kernel or potentially execute code with kernel privileges, leading to denial of service or privilege escalation.

03

Why this severity

The CVSS score of 9.8 reflects the vulnerability’s high impact: it requires no user interaction, can be exploited remotely, and gives attackers full control over the system, leading to complete compromise.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel to a version that includes the fix for the NVMe over TCP use‑after‑free bug.
  2. 02Reboot the system to load the updated kernel.

NVD description

05

Timeline

  1. Jul 4, 2025 · Jul 4, 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 →