CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length
In the Linux kernel, the following vulnerability has been resolved:
nvmet-auth: validate reply message payload bounds against transfer length
nvmetauthreply() 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 DHCHAPREPLY 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 + 2hl) or performs the host response memcmp.
With DH authentication configured, the OOB pointer is passed directly to sginitone() and read by cryptokppcomputesharedsecret(), reaching up to 526 bytes past the buffer. This is exploitable pre-authentication.
Add bounds validation ensuring sizeof(data) + 2hl + dhvlen <= tl before any access to the variable-length fields.
Discovered by Atuin - Automated Vulnerability Discovery Engine.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64319?
The severity of CVE-2026-64319 is critical with a CVSS score of 9.1.
How do I fix CVE-2026-64319?
To fix CVE-2026-64319, update the Linux kernel to a version that addresses this vulnerability.
What impact does CVE-2026-64319 have on system security?
CVE-2026-64319 can allow an attacker to exploit the nvmet-auth component leading to potential data exposure.
Which versions of the Linux kernel are affected by CVE-2026-64319?
CVE-2026-64319 affects specific versions of the Linux kernel that do not validate reply message payload bounds.
Is there a workaround for CVE-2026-64319?
Currently, the recommended response to CVE-2026-64319 is to apply the available kernel updates rather than relying on a workaround.