Local kernel memory access via undersized F3A keymap
Published Jul 25, 2026 · Updated Jul 25, 2026
Out-of-bounds access in affected Linux Kernel releases allows local users to read or write kernel memory through evdev keymap ioctls. rmi_f3a_map_gpios() allocates at most six gpio_key_map entries, while keycodemax and rmi_f3a_attention() use the device-reported GPIO count of up to 127. Access requires an affected RMI F3A device reporting more than six GPIOs and permission to open its evdev node; reads leak adjacent slab data and writes corrupt it.
Summary
What happened
Out-of-bounds access in affected Linux Kernel releases allows local users to read or write kernel memory through evdev keymap ioctls. rmi_f3a_map_gpios() allocates at most six gpio_key_map entries, while keycodemax and rmi_f3a_attention() use the device-reported GPIO count of up to 127. Access requires an affected RMI F3A device reporting more than six GPIOs and permission to open its evdev node; reads leak adjacent slab data and writes corrupt it.
The record
- CVE
- CVE-2026-64277
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, CAPEC-540, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <3480e24bc4e178aaa009edb25b6ee12df199e210
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <35ed74d32d8260bdfb14a94caf402bf0866bdeec
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <502ad7caaa1a445b734c827fa256e5311df67e3d
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <57c10915f2c16c90e0d46ad00876bf39ece40fc2
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <850117b637bcb1dcc14be0cf09ac819a8707b42c
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <8db211aed83733073b0814adaeeab61d4521474e
- Affected versionversion=9e4c596bfd004f447a652205163234dfd4aafa69 <ba57f430328534501962d60d651e385ffd7af9ca
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo