CVE-2026-64237

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

Input: elan_i2c - validate firmware size before use

Ensure that the firmware file is large enough to contain the expected number of pages and the signature (which resides at the end of the firmware blob) before accessing them to prevent potential out-of-bounds reads.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 12, 2026

Advisory Details (8)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

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

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

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

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

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

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76b0d0baa9ae9c60e726bbe1b6ff0bec2c993634
generic

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48b0aa9c08a3ac8e0c0345b7ca581f552324e460
generic

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47b52b98edfe34d0249e72f815215ef24311c3a3
generic

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b37190ad3ded3a15fb1dbfc4f26df520a3e59bb
generic

Input: elan_i2c - validate firmware size before use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/331d49b4e1c9efe4479bbd22922dfcdd8c64be7b

Vendor Advisories for CVE-2026-64237(2)

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

Patch Availability(3)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 119× 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 140 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64237?
CVE-2026-64237 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: elan_i2c - validate firmware size before use Ensure that the firmware file is large enough to contain the expected number of pages and the signature (which resides at the end of the firmware blob) before accessing them to…
When was CVE-2026-64237 disclosed?
CVE-2026-64237 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64237 actively exploited?
CVE-2026-64237 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64237?
CVE-2026-64237 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64237, 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-64237

Explore →

Is Your Infrastructure Affected by CVE-2026-64237?

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