CVE-2026-64276

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count

HIGH
7.8
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count rmi_f30_map_gpios() allocates gpioled_key_map with min(gpioled_count, TRACKSTICK_RANGE_END) == at most 6 entries, but rmi_f30_attention() iterates the full f30->gpioled_count (device query register, range 0..31) and dereferences gpioled_key_map[i], and input->keycodemax is set to the full gpioled_count while input->keycode points at the 6-entry allocation. A device that reports gpioled_count > 6 with GPIO support enabled therefore causes an out-of-bounds read on the attention interrupt and out-of-bounds read/write through the EVIOCGKEYCODE/EVIOCSKEYCODE ioctls, which bound the index only against keycodemax. This is the same defect as the F3A handler, which was copied from F30. Size the keymap for the full gpioled_count; the mapping loop still assigns only the first min(gpioled_count, TRACKSTICK_RANGE_END) entries.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.1 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.963e64fcbdbd10e46dede502d507dbcc104837cd594.144.14 rc74.14 rc8
Vendor states this is fixed in 26c895928d7118436a24f564587cb4aefc40cdd8 (fixed)
Vendor states this is fixed in 4e3689c26854356f41fbaa1eafa382e58ac79e00 (fixed)
Vendor states this is fixed in 8c6d18d61bb6fe0e6edf848413391c590552e8a9 (fixed)
Vendor states this is fixed in bfe622efecd4ff0a792d0ecd1a8dce535a902f50 (fixed)
Vendor states this is fixed in d162a1ead7de404d8b41a093c83ed0db6487cded (fixed)
Vendor states this is fixed in d577e46785d45484b2ab7e7309c49b18764bf56c (fixed)
Vendor states this is fixed in e849c6f51e6877104c765da084e001ec37c8e119 (fixed)
Vendor states this is fixed in f0be9eba946e9200b43265e0a748d38bd0a56954 (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card