In the Linux kernel, the following vulnerability has been resolved: exfat: bound uniname advance in exfat_find_dir_entry() In exfat_find_dir_entry(), each TYPE_EXTEND (file name) entry advances the output pointer by a fixed amount while the loop guard only tracks the accumulated name length: if (++order == 2) uniname = p_uniname->name; else uniname += EXFAT_FILE_NAME_LEN; len = exfat_extract_uni_name(ep, entry_uniname); name_len += len; unichar = *(uniname+len); *(uniname+len) = 0x0; uniname grows by EXFAT_FILE_NAME_LEN (15) per name entry, but name_len grows only by the actual extracted length, which is shorter when a name fragment contains an early NUL. The only guard is `name_len >= MAX_NAME_LENGTH`, so a crafted directory with many short name fragments lets uniname run far past the p_uniname->name[MAX_NAME_LENGTH + 3] buffer while name_len stays small, causing an out-of-bounds read and write at *(uniname+len). The sibling extractor exfat_get_uniname_from_ext_entry()
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-64296 is a buffer overflow vulnerability in the Linux kernel's exfat filesystem implementation, specifically in the exfat_find_dir_entry() function. The flaw occurs when processing extended file name entries—the pointer advancement logic uses a fixed increment (EXFAT_FILE_NAME_LEN) that becomes desynchronized from the actual accumulated name length tracking. This mismatch allows an attacker to write beyond allocated buffer boundaries, potentially enabling arbitrary code execution or denial of service. Any system using exfat filesystems (common in removable media, embedded devices, and cross-platform storage) is affected, particularly those processing untrusted or malicious exfat images.
While CVE-2026-64296 lacks mapped MITRE ATT&CK techniques, Casky's platform using Claude AI with extended reasoning can identify the attack surface by analyzing memory safety violations and exploit primitives. Practitioners using Casky would observe detection patterns related to kernel memory corruption exploitation techniques—specifically looking for evidence of buffer overflow chains, pointer dereference anomalies, and unsafe string handling patterns that map to MITRE T1203 (Exploitation for Privilege Escalation) and T1561 (Disk Wipe) depending on attacker intent. The platform's 754 security skills would flag unsafe boundary conditions, missing validation checks on user-controlled filesystem structures, and unchecked pointer arithmetic—indicators that elevated privileges or kernel exploitation chains are possible entry vectors requiring immediate patching.
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-64296. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation