In the Linux kernel, the following vulnerability has been resolved: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page nvmet_execute_disc_get_log_page() validates only the dword alignment of the host-supplied Log Page Offset (lpo). The 64-bit offset is then added to a small kzalloc'd buffer that holds the discovery log page and the result is passed straight to nvmet_copy_to_sgl(), which memcpy()s data_len bytes out to the host with no source-side bound check: u64 offset = nvmet_get_log_page_offset(req->cmd); /* 64-bit host */ size_t data_len = nvmet_get_log_page_len(req->cmd); /* 32-bit host */ ... if (offset & 0x3) { ... } /* only check */ ... alloc_len = sizeof(*hdr) + entry_size * discovery_log_entries(req); buffer = kzalloc(alloc_len, GFP_KERNEL); ... status = nvmet_copy_to_sgl(req, 0, buffer + offset, data_len); The Discovery controller is unauthenticated -- nvmet_host_allowed() ret
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-64320 is a critical pre-authentication heap buffer over-read vulnerability in the Linux kernel's NVMe target discovery service. An unauthenticated remote attacker can exploit insufficient bounds checking on the Log Page Offset parameter in the Discovery Get Log Page command to read sensitive data from kernel heap memory and transmit it back to the attacker. This vulnerability affects any system exposing NVMe-oF (NVMe over Fabrics) target functionality, potentially allowing information disclosure of cryptographic keys, memory addresses for ASLR bypass, or other sensitive kernel data before authentication occurs.
While CVE-2026-64320 does not currently map to MITRE ATT&CK techniques in public databases, Casky's Claude-powered analysis engine would identify the attack pattern as consistent with T1005 (Data from Local System) combined with pre-authentication access vectors. Practitioners using Casky would observe detection signals focused on: (1) NVMe protocol fuzzing or offset parameter manipulation attempts; (2) unexpected kernel heap memory access patterns in nvmet subsystem logging; (3) Discovery service responses containing out-of-bounds memory content. The platform's extended reasoning would correlate the dword-alignment validation bypass with common kernel exploitation techniques, flagging this as a critical data exfiltration risk requiring immediate kernel patching across NVMe-exposed infrastructure.
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-64320. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation