In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count… (CVE-2026-64277)
A vulnerability in the Linux kernel's synaptics-rmi4 input driver allows out-of-bounds memory access due to improper sizing of the gpio_key_map array. This can lead to out-of-bounds reads and writes when a device reports a gpio_count greater than 6, potentially leaking adjacent kernel memory to user space or allowing writes beyond allocated buffers. The issue arises because the keymap allocation is limited to 6 entries, but the code iterates over the full gpio_count. The fix involves sizing the keymap to the full gpio_count, preventing out-of-bounds access.
AI Analysis
Technical Summary
The Linux kernel synaptics-rmi4 input driver had a vulnerability where the gpio_key_map array was allocated with a maximum of 6 entries, but the code iterated over the full gpio_count (which can be up to 127). This mismatch allowed out-of-bounds reads and writes on gpio_key_map during input events and ioctl calls (EVIOCGKEYCODE and EVIOCSKEYCODE). Specifically, EVIOCGKEYCODE could leak adjacent slab memory to user space, and EVIOCSKEYCODE could write caller-controlled data beyond the allocated buffer. The vulnerability affects any process able to open the evdev node. The patch corrects the allocation size of gpio_key_map to match gpio_count, zero-filling extra entries and preventing out-of-bounds access.
Potential Impact
This vulnerability allows local users with access to the evdev device node to perform out-of-bounds reads and writes in kernel memory. The out-of-bounds read can leak adjacent kernel slab memory to user space, potentially exposing sensitive information. The out-of-bounds write allows a user to write arbitrary values beyond the allocated buffer, which could lead to undefined behavior or kernel memory corruption. However, there is no indication of remote exploitation or widespread active exploitation in the wild.
Mitigation Recommendations
A fix is available that properly sizes the gpio_key_map allocation to the full gpio_count, preventing out-of-bounds access. Users and administrators should update to the patched Linux kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or distribution advisory for the exact fixed kernel versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count… (CVE-2026-64277)
Description
A vulnerability in the Linux kernel's synaptics-rmi4 input driver allows out-of-bounds memory access due to improper sizing of the gpio_key_map array. This can lead to out-of-bounds reads and writes when a device reports a gpio_count greater than 6, potentially leaking adjacent kernel memory to user space or allowing writes beyond allocated buffers. The issue arises because the keymap allocation is limited to 6 entries, but the code iterates over the full gpio_count. The fix involves sizing the keymap to the full gpio_count, preventing out-of-bounds access.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel synaptics-rmi4 input driver had a vulnerability where the gpio_key_map array was allocated with a maximum of 6 entries, but the code iterated over the full gpio_count (which can be up to 127). This mismatch allowed out-of-bounds reads and writes on gpio_key_map during input events and ioctl calls (EVIOCGKEYCODE and EVIOCSKEYCODE). Specifically, EVIOCGKEYCODE could leak adjacent slab memory to user space, and EVIOCSKEYCODE could write caller-controlled data beyond the allocated buffer. The vulnerability affects any process able to open the evdev node. The patch corrects the allocation size of gpio_key_map to match gpio_count, zero-filling extra entries and preventing out-of-bounds access.
Potential Impact
This vulnerability allows local users with access to the evdev device node to perform out-of-bounds reads and writes in kernel memory. The out-of-bounds read can leak adjacent kernel slab memory to user space, potentially exposing sensitive information. The out-of-bounds write allows a user to write arbitrary values beyond the allocated buffer, which could lead to undefined behavior or kernel memory corruption. However, there is no indication of remote exploitation or widespread active exploitation in the wild.
Mitigation Recommendations
A fix is available that properly sizes the gpio_key_map allocation to the full gpio_count, preventing out-of-bounds access. Users and administrators should update to the patched Linux kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update from the vendor or distribution is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or distribution advisory for the exact fixed kernel versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p39g-x9xh-7wq9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64277"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420f9c2644c7f80868d1
Added to database: 07/25/2026, 23:09:03 UTC
Last enriched: 07/25/2026, 23:41:49 UTC
Last updated: 07/26/2026, 00:12:09 UTC
Views: 2
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.