In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count rmi_f30_map_gpios() allocates gpioled_key_map with min(gpioled_count, TRACKSTICK_RANGE_END) == at most 6 entries, but rmi_f30_attention() iterates the full f30->gpioled_count (device query register, range 0..31) and dereferences gpioled_key_map[i], and input->keycodemax is set to the full gpioled_count while input->keycode points at the 6-entry allocation. A device that reports gpioled_count > 6 with GPIO support enabled therefore causes an out-of-bounds read on the attention interrupt and out-of-bounds read/write through the EVIOCGKEYCODE/EVIOCSKEYCODE ioctls, which bound the index only against keycodemax. This is the same defect as the F3A handler, which was copied from F30. Size the keymap for the full gpioled_count; the mapping loop still assigns only the first min(gpioled_count, TRACKSTICK_RANGE_END) entries.
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-64276 is a buffer overread vulnerability in the Linux kernel's Synaptics RMI4 input driver affecting the F30 GPIO/LED keymap handling. The vulnerability occurs when the driver allocates a gpioled_key_map array bounded to a maximum of 6 entries, but then iterates through the full gpioled_count value (0-31 from device registers) during attention handling, causing out-of-bounds memory access. This affects any system using Synaptics RMI4 touchpad controllers, particularly enterprise laptops and workstations. The vulnerability could lead to information disclosure or denial of service if an attacker can trigger the attention handler through malicious device input or firmware manipulation.
While CVE-2026-64276 lacks mapped MITRE ATT&CK techniques, Casky's Claude AI-powered analysis would identify this as a classic Memory Access Violation pattern associated with T1203 (Exploitation for Privilege Escalation) and T1499 (Endpoint Denial of Service). Security practitioners using Casky would see findings highlighting improper input validation in kernel drivers, array bounds checking failures, and unsafe memory dereferencing—patterns that precede kernel exploitation attempts. The extended reasoning capability would correlate this kernel-level memory safety issue with post-exploitation persistence techniques, as compromised kernel memory could enable rootkit installation or privilege escalation chains targeting high-value endpoints.
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-64276. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation