Answer in brief
CVE-2026-64276 records a High severity (CVSS 7.8) vulnerability in Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.14:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.14:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.14:rc8:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <8c6d18d61bb6fe0e6edf848413391c590552e8a9 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <d162a1ead7de404d8b41a093c83ed0db6487cded || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <f0be9eba946e9200b43265e0a748d38bd0a56954 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <26c895928d7118436a24f564587cb4aefc40cdd8 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <4e3689c26854356f41fbaa1eafa382e58ac79e00 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <e849c6f51e6877104c765da084e001ec37c8e119 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <bfe622efecd4ff0a792d0ecd1a8dce535a902f50 || >=3e64fcbdbd10e46dede502d507dbcc104837cd59 <d577e46785d45484b2ab7e7309c49b18764bf56c | 8c6d18d61bb6fe0e6edf848413391c590552e8a9, d162a1ead7de404d8b41a093c83ed0db6487cded, f0be9eba946e9200b43265e0a748d38bd0a56954, 26c895928d7118436a24f564587cb4aefc40cdd8, 4e3689c26854356f41fbaa1eafa382e58ac79e00, e849c6f51e6877104c765da084e001ec37c8e119, bfe622efecd4ff0a792d0ecd1a8dce535a902f50, d577e46785d45484b2ab7e7309c49b18764bf56c |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.