CVE-2026-64276

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f0be9eba946e9200b43265e0a748d38bd0a56954
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e849c6f51e6877104c765da084e001ec37c8e119
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d577e46785d45484b2ab7e7309c49b18764bf56c
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d162a1ead7de404d8b41a093c83ed0db6487cded
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfe622efecd4ff0a792d0ecd1a8dce535a902f50
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c6d18d61bb6fe0e6edf848413391c590552e8a9
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e3689c26854356f41fbaa1eafa382e58ac79e00
generic

Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26c895928d7118436a24f564587cb4aefc40cdd8

Vendor Advisories for CVE-2026-64276(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.158.1.rt7.499.el8_102026-08-26redhat
redhatkernel-0:4.18.0-553.158.1.el8_102026-08-26redhat
redhatkernel-0:5.14.0-687.42.1.el9_82026-08-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 29× in last 7d / 149× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:12 UTCEG score recompute
  3. 2026-08-30 00:12 UTCVendor advisory
  4. 2026-08-30 00:12 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:40 UTCEG score recompute
  7. 2026-08-27 21:40 UTCVendor advisory
  8. 2026-08-27 21:40 UTCGHSA enrichment
  9. 2026-08-27 09:58 UTCVendor advisory
  10. 2026-08-27 09:58 UTCGHSA enrichment
  11. 2026-08-26 19:51 UTCEG score recompute
  12. 2026-08-26 19:51 UTCVendor advisory
  13. 2026-08-26 19:51 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 05:38 UTCVendor advisory
  16. 2026-08-26 05:38 UTCGHSA enrichment
  17. 2026-08-25 17:44 UTCEG score recompute
  18. 2026-08-25 17:44 UTCVendor advisory
  19. 2026-08-25 17:44 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 05:46 UTCVendor advisory
  22. 2026-08-25 05:46 UTCGHSA enrichment
  23. 2026-08-24 18:03 UTCEG score recompute
  24. 2026-08-24 18:03 UTCVendor advisory
  25. 2026-08-24 18:03 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 05:37 UTCVendor advisory
  2. 2026-08-24 05:37 UTCGHSA enrichment
  3. 2026-08-23 17:55 UTCVendor advisory
  4. 2026-08-23 17:55 UTCGHSA enrichment
  5. 2026-08-23 06:13 UTCEG score recompute
  6. 2026-08-23 06:13 UTCVendor advisory
  7. 2026-08-23 06:13 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 18:30 UTCVendor advisory
  10. 2026-08-22 18:30 UTCGHSA enrichment
  11. 2026-08-22 06:47 UTCEG score recompute
  12. 2026-08-22 06:47 UTCVendor advisory
  13. 2026-08-22 06:47 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 19:05 UTCGHSA enrichment
  16. 2026-08-21 07:23 UTCEG score recompute
  17. 2026-08-21 07:23 UTCVendor advisory
  18. 2026-08-21 07:23 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 19:40 UTCVendor advisory
  21. 2026-08-20 19:40 UTCGHSA enrichment
  22. 2026-08-20 07:58 UTCVendor advisory
  23. 2026-08-20 07:58 UTCGHSA enrichment
  24. 2026-08-19 20:16 UTCEG score recompute
  25. 2026-08-19 20:16 UTCVendor advisory
  26. 2026-08-19 20:16 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 06:49 UTCVendor advisory
  29. 2026-08-19 06:49 UTCGHSA enrichment
  30. 2026-08-18 18:51 UTCEG score recompute
  31. 2026-08-18 18:51 UTCVendor advisory
  32. 2026-08-18 18:51 UTCGHSA enrichment
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-18 04:46 UTCGHSA enrichment
  35. 2026-08-17 17:03 UTCEG score recompute
  36. 2026-08-17 17:03 UTCVendor advisory
  37. 2026-08-17 17:03 UTCGHSA enrichment
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 05:21 UTCEG score recompute
  40. 2026-08-17 05:21 UTCVendor advisory
  41. 2026-08-17 05:21 UTCGHSA enrichment
  42. 2026-08-17 04:25 UTCVendor advisory
  43. 2026-08-17 04:25 UTCGHSA enrichment
  44. 2026-08-16 16:43 UTCEG score recompute
  45. 2026-08-16 16:43 UTCVendor advisory
  46. 2026-08-16 16:43 UTCGHSA enrichment
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 05:01 UTCEG score recompute
  49. 2026-08-16 05:01 UTCVendor advisory
  50. 2026-08-16 05:01 UTCGHSA enrichment
  51. 2026-08-15 17:19 UTCVendor advisory
  52. 2026-08-15 17:19 UTCGHSA enrichment
  53. 2026-08-15 05:37 UTCEG score recompute
  54. 2026-08-15 05:37 UTCVendor advisory
  55. 2026-08-15 05:37 UTCGHSA enrichment
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 17:54 UTCVendor advisory
  58. 2026-08-14 17:54 UTCGHSA enrichment
  59. 2026-08-14 06:12 UTCEG score recompute
  60. 2026-08-14 06:12 UTCVendor advisory
  61. 2026-08-14 06:12 UTCGHSA enrichment
  62. 2026-08-13 22:00 UTCEPSS rescore
  63. 2026-08-13 18:30 UTCEG score recompute
  64. 2026-08-13 18:30 UTCVendor advisory
  65. 2026-08-13 18:30 UTCGHSA enrichment
  66. 2026-08-13 08:30 UTCVendor advisory
  67. 2026-08-13 08:30 UTCGHSA enrichment
  68. 2026-08-12 20:48 UTCEG score recompute
  69. 2026-08-12 20:48 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 09:06 UTCVendor advisory
  72. 2026-08-12 09:06 UTCGHSA enrichment
  73. 2026-08-11 21:24 UTCVendor advisory
  74. 2026-08-11 21:24 UTCGHSA enrichment
  75. 2026-08-11 09:42 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64276?
CVE-2026-64276 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count rmif30mapgpios() allocates gpioledkey_map with min(gpioledcount, TRACKSTICKRANGE_END) == at most 6 entries, but rmif30attention() iterates the full…
When was CVE-2026-64276 disclosed?
CVE-2026-64276 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64276 actively exploited?
CVE-2026-64276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64276?
CVE-2026-64276 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64276, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64276

Explore →

Is Your Infrastructure Affected by CVE-2026-64276?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs