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

CVE-2026-64534

A critical bug in the Linux kernel’s NVMe over TCP implementation can cause a reference‑count underflow, leading to a warning, use‑after‑free, and a permanent workqueue deadlock. The flaw occurs when a data‑digest mismatch is detected and the request cleanup is performed without checking if initialization failed. The issue has been fixed in the kernel.

publishedJul 27, 2026
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
31th 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, specifically the NVMe over TCP (nvmet‑tcp) subsystem. Users running kernel versions before the fix are affected, including servers and systems that use NVMe over TCP for storage.

02

Real-world impact

An attacker could trigger a permanent deadlock in the kernel’s workqueue, potentially causing a denial of service by halting system operations. The vulnerability could also lead to a use‑after‑free condition, which might be exploitable for arbitrary code execution if combined with other weaknesses.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability is exploitable over the network with no authentication or user interaction, and it can lead to complete compromise of confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the nvmet-tcp fix.

NVD description indicates the vulnerability has been resolved.

05

Timeline

  1. Jul 27, 2026 · 5d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 2d 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 →