← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-64535

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-64535

Key Details

CVECVE-2026-64535
CVSS Score / Version
9.8 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-64535
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-64535
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.