CVE-2026-64277 is an out-of-bounds memory-access vulnerability in the Linux kernel Synaptics RMI4 input driver's F3A keymap handling. The driver accepts a device-reported GPIO count of up to 127, but allocated its GPIO keymap for no more than six entries. The attention handler subsequently iterated over the full reported count, causing out-of-bounds reads when the count exceeded six. Additionally, the input device keycode maximum reflected the full GPIO count despite the smaller backing allocation. Consequently, default evdev keymap ioctl handlers could access memory beyond the keymap because they validated indexes against the reported maximum rather than the allocation size. The fix allocates the keymap for the complete reported GPIO count; entries beyond the supported trackstick mapping range remain KEY_RESERVED.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced in the Oracle Linux 8 kernel-related security advisory; no technical flaw details are provided.
A vulnerability addressed by the Oracle Linux 9 kernel security update.
Linux kernel Synaptics RMI4 input-driver flaw involving failure to bound the F3A keymap to the GPIO count.
Linux kernel Synaptics RMI4 input-driver flaw involving failure to bound the F3A keymap to the GPIO count.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.