In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event. Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows: CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1 munmap the page [6]: free rb->aux_pages[0] Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed ph
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-64300 is a use-after-free (UAF) vulnerability in the Linux kernel's performance monitoring (perf) subsystem that affects the auxiliary ring buffer (aux) handling. The vulnerability arises from a race condition in the map_range() function when multiple performance events share the same ring buffer through PERF_EVENT_IOC_SET_OUTPUT. The issue occurs because map_range() accesses shared ring buffer fields (aux_pages[], aux_nr_pages, and aux_pgoff) while holding only a per-event mutex, while these fields are actually protected by a different mutex (aux_mutex) at the ring buffer level. This synchronization mismatch allows two events to race, with one event reallocating the auxiliary pages while another is still mapping them, resulting in a page use-after-free condition. This vulnerability affects any Linux system running vulnerable kernel versions where users can create and manipulate performance monitoring events, potentially allowing local privilege escalation or denial of service.
Casky.ai's Claude-powered analysis would identify this vulnerability through detection of memory safety violations and synchronization bypass patterns, even without explicit MITRE ATT&CK mappings. The platform's 754 security skills would flag suspicious perf subsystem activity including: (1) abnormal patterns in perf_event_open() syscall sequences with shared ring buffers, (2) timing-based anomalies in rapid PERF_EVENT_IOC_SET_OUTPUT calls followed by memory access, and (3) system behaviors consistent with use-after-free exploitation such as kernel memory corruption or unexpected crashes in perf-related operations. Extended reasoning capabilities would correlate low-level kernel synchronization failures with potential Privilege Escalation and Resource Exhaustion attack patterns, helping practitioners identify exploitation attempts even when attackers attempt to obfuscate the underlying race condition.
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-64300. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation