In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count… (CVE-2026-64276)
A vulnerability in the Linux kernel's synaptics-rmi4 input driver allowed out-of-bounds read and write operations due to improper sizing of the gpioled_key_map array. This occurred when a device reported a gpioled_count greater than 6, leading to memory access beyond the allocated array during interrupt handling and ioctl operations. The issue was fixed by correctly sizing the keymap to the full gpioled_count while maintaining the original mapping logic.
AI Analysis
Technical Summary
The Linux kernel synaptics-rmi4 driver had a vulnerability (CVE-2026-64276) where the gpioled_key_map array was allocated with a size limited to min(gpioled_count, 6), but subsequent code iterated over the full gpioled_count (up to 31), causing out-of-bounds memory accesses. This affected the rmi_f30_attention interrupt handler and EVIOCGKEYCODE/EVIOCSKEYCODE ioctls, which used keycodemax set to gpioled_count but referenced the smaller allocated array. The fix involved allocating gpioled_key_map with the full gpioled_count size, preventing out-of-bounds access.
Potential Impact
Devices reporting gpioled_count values greater than 6 with GPIO support enabled could trigger out-of-bounds reads and writes in kernel memory during interrupt handling and ioctl operations. This could potentially lead to kernel memory corruption or crashes. However, no known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved in the Linux kernel by properly sizing the gpioled_key_map allocation. Users should monitor official Linux kernel advisories and update to a fixed kernel version once available.
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count… (CVE-2026-64276)
Description
A vulnerability in the Linux kernel's synaptics-rmi4 input driver allowed out-of-bounds read and write operations due to improper sizing of the gpioled_key_map array. This occurred when a device reported a gpioled_count greater than 6, leading to memory access beyond the allocated array during interrupt handling and ioctl operations. The issue was fixed by correctly sizing the keymap to the full gpioled_count while maintaining the original mapping logic.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel synaptics-rmi4 driver had a vulnerability (CVE-2026-64276) where the gpioled_key_map array was allocated with a size limited to min(gpioled_count, 6), but subsequent code iterated over the full gpioled_count (up to 31), causing out-of-bounds memory accesses. This affected the rmi_f30_attention interrupt handler and EVIOCGKEYCODE/EVIOCSKEYCODE ioctls, which used keycodemax set to gpioled_count but referenced the smaller allocated array. The fix involved allocating gpioled_key_map with the full gpioled_count size, preventing out-of-bounds access.
Potential Impact
Devices reporting gpioled_count values greater than 6 with GPIO support enabled could trigger out-of-bounds reads and writes in kernel memory during interrupt handling and ioctl operations. This could potentially lead to kernel memory corruption or crashes. However, no known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved in the Linux kernel by properly sizing the gpioled_key_map allocation. Users should monitor official Linux kernel advisories and update to a fixed kernel version once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7j4q-9mx8-7779
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64276"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420f9c2644c7f8086908
Added to database: 07/25/2026, 23:09:03 UTC
Last enriched: 07/25/2026, 23:42:39 UTC
Last updated: 07/26/2026, 05:33:55 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.