CVE-2026-64097drm/amd/display: Validate GPIO pin LUT table size before iterating
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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)
Timeline
ID reserved
By Linux
Published
- 3 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < 9900f6954be779011e7c2cd42addd87baf028bc5
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < fb30a3890d62fd50a95aef684faf64a307592e42
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < 67461e0c15335894cc5d3b84cda823bf8cbdc886
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < f2a4827e980ba07de4391fa84d9c39a12726bdd7
- affected ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – < 86d2b20644b11d21fe52c596e6e922b4590a3e3f
- affected 4.15
- unaffected < 4.15
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.142 – ≤ 6.6.*
- unaffected 6.12.92 – ≤ 6.12.*
- unaffected 6.18.34 – ≤ 6.18.*
- unaffected 7.0.11 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/9900f6954be779011e7c2cd42addd87baf028bc5 (opens in a new tab)
- https://git.kernel.org/stable/c/fb30a3890d62fd50a95aef684faf64a307592e42 (opens in a new tab)
- https://git.kernel.org/stable/c/67461e0c15335894cc5d3b84cda823bf8cbdc886 (opens in a new tab)
- https://git.kernel.org/stable/c/7ca695b3122297b06a3ed605bbe1cd32c85d9f5a (opens in a new tab)
- https://git.kernel.org/stable/c/f2a4827e980ba07de4391fa84d9c39a12726bdd7 (opens in a new tab)
- https://git.kernel.org/stable/c/86d2b20644b11d21fe52c596e6e922b4590a3e3f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45782 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64097)Record last updated .