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

CVE-2026-64319

Last refreshed2026-10-17

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

Key Details

CVECVE-2026-64319
CVSS Score / Version
9.1 (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:N/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 none; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-125 (Out-of-bounds Read)

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-auth: validate reply message payload bounds against transfer length

nvmet_auth_reply() accesses the variable-length rval[] array using

attacker-controlled hl (hash length) and dhvlen (DH value length) fields

without verifying they fit within the allocated buffer of tl bytes.

A malicious NVMe-oF initiator can craft a DHCHAP_REPLY message with a

small transfer length but large hl/dhvlen values, causing out-of-bounds

heap reads when the target processes the DH public key (rval + 2*hl) or

performs the host response memcmp.

With DH authentication configured, the OOB pointer is passed directly to

sg_init_one() and read by crypto_kpp_compute_shared_secret(), reaching

up to 526 bytes past the buffer. This is exploitable pre-authentication.

Add bounds validation ensuring sizeof(*data) + 2*hl + dhvlen <= tl before

any access to the variable-length fields.

Discovered by Atuin - Automated Vulnerability Discovery Engine. (NVD)

What to Do

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

References

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