CVE-2026-64097

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated 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:

drm/amd/display: Validate GPIO pin LUT table size before iterating

[Why&How] The GPIO pin table parsers in get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() derive an element count from the VBIOS table_header.structuresize field, then iterate over gpio_pin[] entries. However, GET_IMAGE() only validates that the table header itself fits within the BIOS image. If the VBIOS reports a structuresize larger than the actual mapped data, the loop reads past the end of the BIOS image, causing an out-of-bounds read.

Fix this by calling bios_get_image() to validate that the full claimed structuresize is accessible within the BIOS image before entering the loop in both functions.

(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)

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
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 11, 2026

Advisory Details (6)

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

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9900f6954be779011e7c2cd42addd87baf028bc5
generic

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86d2b20644b11d21fe52c596e6e922b4590a3e3f
generic

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ca695b3122297b06a3ed605bbe1cd32c85d9f5a
generic

drm/amd/display: Validate GPIO pin LUT table size before iterating - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67461e0c15335894cc5d3b84cda823bf8cbdc886

Vendor Advisories for CVE-2026-64097(2)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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 ... 7.2~rc5-1~exp1 (496 versions)——
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

(5)

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 29× in last 7d / 157× 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 208 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64097?
CVE-2026-64097 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The GPIO pin table parsers in getgpioi2c_info() and biosparsergetgpiopin_info() derive an element count from the VBIOS tableheader.structuresize field,…
When was CVE-2026-64097 disclosed?
CVE-2026-64097 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64097 actively exploited?
CVE-2026-64097 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64097?
CVE-2026-64097 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64097, 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-64097

Explore →

Is Your Infrastructure Affected by CVE-2026-64097?

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

Start Free Scan →Browse All CVEs