In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry(), the buffer_head obtained from exfat_get_dentry() is released with brelse(bh) before the fall-through TYPE_EXTEND branch reads the directory entry through ep (which points into bh->b_data): brelse(bh); if (entry_type == TYPE_EXTEND) { ... len = exfat_extract_uni_name(ep, entry_uniname); ... } After brelse() drops our reference, nothing guarantees that the underlying page backing bh->b_data remains valid for the subsequent exfat_extract_uni_name() read. This is the same pattern fixed in commit fc961522ddbd ("exfat: Fix potential use after free in exfat_load_upcase_table()"). Move brelse(bh) so it runs after ep is no longer dereferenced on each branch. Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y + CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image (long filename with same-hash
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-63808 is a critical use-after-free vulnerability in the Linux kernel's exfat filesystem implementation, specifically in the exfat_find_dir_entry() function. The flaw occurs when a buffer_head structure is released via brelse() while a pointer (ep) still references data within that buffer's memory region. Subsequent operations attempt to read directory entry data through the freed pointer, potentially allowing local attackers to corrupt kernel memory, trigger denial of service, or achieve privilege escalation. This affects any Linux system using exfat filesystems, including embedded devices, IoT systems, and general-purpose Linux distributions that support removable storage.
While CVE-2026-63808 lacks mapped MITRE ATT&CK techniques in its current advisory, Casky's Claude-powered analysis identifies this as a classic memory safety violation pattern relevant to Defense Evasion and Privilege Escalation attack chains. Practitioners using Casky would observe detection correlations around memory corruption exploitation techniques (T1190: Exploit Public-Facing Application, T1068: Exploitation for Privilege Escalation) and underlying CWE-416 patterns. Security teams monitoring kernel exploit attempts would see this vulnerability classified alongside heap/use-after-free exploitation signatures. Casky's extended reasoning capabilities help practitioners understand that even though direct ATT&CK mappings are unavailable, the underlying memory safety flaw represents a critical kernel hardening gap that adversaries actively target in privilege escalation chains, requiring immediate patch deployment and filesystem access restrictions.
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-63808. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation