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

CVE-2026-64277

Linux

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

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

Affected product and versions

Product
Linux
Affected versions
>= 9e4c596bfd004f447a652205163234dfd4aafa69 < 502ad7caaa1a445b734c827fa256e5311df67e3d, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 3480e24bc4e178aaa009edb25b6ee12df199e210, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 35ed74d32d8260bdfb14a94caf402bf0866bdeec, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < ba57f430328534501962d60d651e385ffd7af9ca, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 850117b637bcb1dcc14be0cf09ac819a8707b42c, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 8db211aed83733073b0814adaeeab61d4521474e, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42, >= 9e4c596bfd004f447a652205163234dfd4aafa69 < 57c10915f2c16c90e0d46ad00876bf39ece40fc2, >= 5.10
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