CVE-2026-64535

nvmet-tcp: Fix potential UAF when ddgst mismatch

CRITICAL
9.8
CVSS Score
Published: July 27, 2026 at 06:32 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.8
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4b17476d809273617d3317fa0d4ae78aa488d7605.10.205.11.35.1291edfca6f8b364d60cde3ddefaf7d03ddf35774bfda871c0ba5d2eed2cd1c881573168129da70058
Vendor states this is fixed in 088ee46c18d99baef453afd74181dd40ade044ad (fixed)
Vendor states this is fixed in 6f9442983a3e4227afd1c83a5251ddbca585ea21 (fixed)
Vendor states this is fixed in 7e558308eba14c8136cb1e615f0c850f76d1fc0a (fixed)
Vendor states this is fixed in 96fe2513df590e74b04253a45089cae75569570e (fixed)
Vendor states this is fixed in dbbd07d0a7020b80f6a7028e561908f7b83b3d5a (fixed)
Vendor states this is fixed in dfb902462bca478f050224ec7a7195aafa7643b1 (fixed)
Vendor states this is fixed in e091ff83d962f9ed00d9bd70443676de9fe98bdc (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

9.8CRITICALLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-415

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card