CVE-2026-64277
Last modified
CVE-2026-64277 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count rmi_f3a_initialize() takes the GPIO count from the device query register (f3a->gpio_count = buf & RMI_F3A_GPIO_COUNT, range 0..127). rmi_f3a_map_gpios() then allocates gpio_key_map with min(gpio_count, TRACKSTICK_RANGE_END) == at most 6 entries, but rmi_f3a_attention() iterates the full gpio_count and dereferences gpio_key_map[i], and input->keycodemax is set to the full gpio_count while input->keycode points at the 6-entry allocation. A device that reports gpio_count > 6 therefore causes an out-of-bounds read of gpio_key_map[] on every attention interrupt, and out-of-bounds accesses through the input core's default keymap ioctls: EVIOCGKEYCODE reads past the buffer (leaking adjacent slab memory to user space) and EVIOCSKEYCODE writes a caller-controlled value past it, for any process able to open the evdev node, since input_default_getkeycode() and input_default_setkeycode() only bound the index against keycodemax. Size the keymap for the full gpio_count. The mapping loop is unchanged: it still assigns only the first min(gpio_count, TRACKSTICK_RANGE_END) entries; the remaining slots stay KEY_RESERVED (devm_kcalloc zero-fills) and are skipped when reporting.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count rmi_f3a_initialize() takes the GPIO count from the device query register (f3a->gpio_count = buf & RMI_F3A_GPIO_COUNT, range 0..127). rmi_f3a_map_gpios() then allocates gpio_key_map with min(gpio_count, TRACKSTICK_RANGE_END) == at most 6 entries, but rmi_f3a_attention() iterates the full gpio_count and dereferences gpio_key_map[i], and input->keycodemax is set to the full gpio_count while input->keycode points at the 6-entry allocation. A device that reports gpio_count > 6 therefore causes an out-of-bounds read of gpio_key_map[] on every attention interrupt, and out-of-bounds accesses through the input core's default keymap ioctls: EVIOCGKEYCODE reads past the buffer (leaking adjacent slab memory to user space) and EVIOCSKEYCODE writes a caller-controlled value past it, for any process able to open the evdev node, since input_default_getkeycode() and input_default_setkeycode() only bound the index against keycodemax. Size the keymap for the full gpio_count. The mapping loop is unchanged: it still assigns only the first min(gpio_count, TRACKSTICK_RANGE_END) entries; the remaining slots stay KEY_RESERVED (devm_kcalloc zero-fills) and are skipped when reporting.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 502ad7caaa1a445b734c827fa256e5311df67e3d; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 3480e24bc4e178aaa009edb25b6ee12df199e210; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 35ed74d32d8260bdfb14a94caf402bf0866bdeec; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < ba57f430328534501962d60d651e385ffd7af9ca; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 850117b637bcb1dcc14be0cf09ac819a8707b42c; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 8db211aed83733073b0814adaeeab61d4521474e; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42; >= 9e4c596bfd004f447a652205163234dfd4aafa69, < 57c10915f2c16c90e0d46ad00876bf39ece40fc2 |
| Linux | Linux | 5.10 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64277?
How severe is CVE-2026-64277?
How do I fix CVE-2026-64277?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64271In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64272In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64273In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64274In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64275In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64276In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64278In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64279In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6428SQL Injection in reports/catalogue_out.pl in Koha Community …7.6
- CVE-2026-64280In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64281In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64282In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-64277?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
