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

CVE-2026-64320

A flaw in the Linux kernel’s NVMe target discovery feature lets an unauthenticated network peer read memory or crash the system before authentication. By sending a specially crafted Get Log Page request with an out‑of‑bounds offset, an attacker can cause the kernel to copy data beyond the intended buffer, exposing kernel pointers or triggering a crash. The vulnerability is critical because it can be triggered by any host that can reach the NVMe target over TCP, RDMA, or Fibre Channel.

publishedJul 25, 2026
last modifiedJul 27, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
51th 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 26, 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 nvmet (NVMe target) component. Any system running an unpatched kernel that exposes an NVMe target over TCP, RDMA, or Fibre Channel is affected.

02

Real-world impact

An attacker can read kernel memory contents or crash the target, potentially leading to information disclosure or denial of service.

03

Why this severity

The CVSS score of 9.1 reflects that the vulnerability is exploitable over the network without authentication, has low attack complexity, and can cause complete loss of confidentiality and availability. The lack of user interaction and the ability to read arbitrary kernel memory make it highly dangerous.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the nvmet patch that fixes the out‑of‑bounds heap read in Discovery Get Log Page.
  2. 02Reboot or restart the system to load the updated kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 25, 2026 · 7d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 27, 2026 · 5d 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 impactNone
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 →