Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64277Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64277, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 502ad7caaa1a445b734c827fa256e5311df67e3d
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 3480e24bc4e178aaa009edb25b6ee12df199e210
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 35ed74d32d8260bdfb14a94caf402bf0866bdeec
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < ba57f430328534501962d60d651e385ffd7af9ca
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 850117b637bcb1dcc14be0cf09ac819a8707b42c
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 8db211aed83733073b0814adaeeab61d4521474e
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 64fb0e1161ccc6b9e48b8df61f07d3c34c01ec42
    • affected 9e4c596bfd004f447a652205163234dfd4aafa69 – < 57c10915f2c16c90e0d46ad00876bf39ece40fc2
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64277 badge
[![CVE-2026-64277](https://cveledger.app/badge/CVE-2026-64277.svg)](https://cveledger.app/cve/CVE-2026-64277)

Record last updated .