SECUFOCUSNOW
Home›CVE index›CVE-2026-64276
Review reviewHigh

CVE-2026-64276

Linux

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 rea...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 rea...

Affected product and versions

Product
Linux
Affected versions
>= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < 8c6d18d61bb6fe0e6edf848413391c590552e8a9, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < d162a1ead7de404d8b41a093c83ed0db6487cded, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < f0be9eba946e9200b43265e0a748d38bd0a56954, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < 26c895928d7118436a24f564587cb4aefc40cdd8, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < 4e3689c26854356f41fbaa1eafa382e58ac79e00, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < e849c6f51e6877104c765da084e001ec37c8e119, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < bfe622efecd4ff0a792d0ecd1a8dce535a902f50, >= 3e64fcbdbd10e46dede502d507dbcc104837cd59 < d577e46785d45484b2ab7e7309c49b18764bf56c, >= 4.14
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available