Kernel heap read and write via undersized keymap
Published Jul 25, 2026 · Updated Jul 25, 2026
Out-of-bounds access in the Linux Kernel allows local users to read or write kernel heap memory through evdev keycode ioctls. rmi_f30_map_gpios() allocates at most six keymap entries while keycodemax and rmi_f30_attention() use the device-reported GPIO/LED count of up to 31. Reachability requires an affected Synaptics RMI4 F30 device with GPIO support and permission to open its event node; crafted indices trigger two-byte heap reads or writes.
Summary
What happened
Out-of-bounds access in the Linux Kernel allows local users to read or write kernel heap memory through evdev keycode ioctls. rmi_f30_map_gpios() allocates at most six keymap entries while keycodemax and rmi_f30_attention() use the device-reported GPIO/LED count of up to 31. Reachability requires an affected Synaptics RMI4 F30 device with GPIO support and permission to open its event node; crafted indices trigger two-byte heap reads or writes.
The record
- CVE
- CVE-2026-64276
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- 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=3e64fcbdbd10e46dede502d507dbcc104837cd59 <26c895928d7118436a24f564587cb4aefc40cdd8
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <4e3689c26854356f41fbaa1eafa382e58ac79e00
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <8c6d18d61bb6fe0e6edf848413391c590552e8a9
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <bfe622efecd4ff0a792d0ecd1a8dce535a902f50
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <d162a1ead7de404d8b41a093c83ed0db6487cded
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <d577e46785d45484b2ab7e7309c49b18764bf56c
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <e849c6f51e6877104c765da084e001ec37c8e119
- Affected versionversion=3e64fcbdbd10e46dede502d507dbcc104837cd59 <f0be9eba946e9200b43265e0a748d38bd0a56954
- Affected versionversion=4.14
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