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
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-64319 is a critical heap buffer overflow vulnerability in the Linux kernel's NVMe-oF (NVMe over Fabrics) authentication handler. The nvmet_auth_reply() function fails to validate that attacker-controlled hash length (hl) and Diffie-Hellman value length (dhvlen) fields fit within the allocated reply message buffer before accessing the rval[] array. A malicious NVMe-oF initiator can exploit this by crafting a specially crafted DHCHAP_REPLY message with a small transfer length but oversized hl/dhvlen values, triggering an out-of-bounds heap read or write. This affects Linux systems running NVMe-oF target implementations, impacting storage infrastructure and hypervisors that expose NVMe services to untrusted networks, with a CVSS score of 9.1 indicating severe risk of system compromise.
While Casky currently shows zero matching skills for this specific CVE, Claude AI's extended reasoning capabilities would identify the underlying attack pattern as a variant of CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer). Practitioners using Casky should monitor for evidence of Exploitation (MITRE ATT&CK T1190) attempts against NVMe-oF services, including malformed protocol messages in kernel logs or unexpected memory access patterns. The detection strategy would focus on input validation gaps—specifically, tracking cases where user-supplied length fields bypass bounds checking before array access—combined with privilege escalation indicators (T1134) that follow successful heap corruption. As the threat landscape evolves, Casky's skill library will expand to map such memory safety vulnerabilities to attack chains, enabling practitioners to correlate suspicious NVMe authentication traffic with post-exploitation lateral movement.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-64319. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation