CVE-2026-64319: Linux Kernel out-of-bounds read (CVSS 9.1)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

Linux Kernel≥ 6.0 < 6.6.145 · ≥ 6.13 < 6.18.39 · ≥ 6.19 < 7.1.4 · ≥ 6.7 < 6.12.96

Remediation

Fixed in

Linux Kernel≥ 6.6.145

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-64319 being actively exploited?

CVE-2026-64319 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.52%.

How severe is CVE-2026-64319?

CVE-2026-64319 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.52% probability of exploitation.

Which products are affected by CVE-2026-64319?

Affected products include Linux Kernel.

How do I fix CVE-2026-64319?

Upgrade affected software to a fixed version, for example Linux Kernel 6.6.145 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-64319 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo