CVE-2026-64277Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 9e4c596bfd004f447a652205163234dfd4aafa69 before 502ad7caaa1a445b734c827fa256e5311df67e3d; from 9e4c596bfd004f447a652205163234dfd4aafa69 before 3480e24bc4e178aaa009edb25b6ee12df199e210; from 9e4c596bfd004f447a652205163234dfd4aafa69 before 35ed74d32d8260bdfb14a94caf402bf0866bdeec; from 9e4c596bfd004f447a652205163234dfd4aafa69 before ba57f430328534501962d60d651e385ffd7af9ca; from 9e4c596bfd004f447a652205163234dfd4aafa69 before 850117b637bcb1dcc14be0cf09ac819a8707b42c; 9e4c596bfd004f447a652205163234dfd4aafa69 builds before 8db211aed83733073b0814adaeeab61d4521474e; from 9e4c596bfd004f447a652205163234dfd4aafa69 before 64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42; from 9e4c596bfd004f447a652205163234dfd4aafa69 before 57c10915f2c16c90e0d46ad00876bf39ece40fc2 | CNA record |
linux linux_kernel linux:linux_kernel | from 5.10 before 5.10.261; from 5.11 before 5.15.212; from 5.16 before 6.1.178; from 6.2 before 6.6.145; from 6.7 before 6.12.96; from 6.13 before 6.18.39; from 6.19 before 7.1.4 | NVD |
References
- https://git.kernel.org/stable/c/502ad7caaa1a445b734c827fa256e5311df67e3dpatch
- https://git.kernel.org/stable/c/3480e24bc4e178aaa009edb25b6ee12df199e210patch
- https://git.kernel.org/stable/c/35ed74d32d8260bdfb14a94caf402bf0866bdeecpatch
- https://git.kernel.org/stable/c/ba57f430328534501962d60d651e385ffd7af9capatch
- https://git.kernel.org/stable/c/850117b637bcb1dcc14be0cf09ac819a8707b42cpatch
- https://git.kernel.org/stable/c/8db211aed83733073b0814adaeeab61d4521474epatch
- https://git.kernel.org/stable/c/64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42patch
- https://git.kernel.org/stable/c/57c10915f2c16c90e0d46ad00876bf39ece40fc2patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.