CVE-2026-64097

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

HIGH
7.8
CVSS Score
Published: July 19, 2026 at 03:40 PM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.15 ≤ v < 6.1.1756.13 ≤ v < 6.18.346.19 ≤ v < 7.0.116.2 ≤ v < 6.6.1426.7 ≤ v < 6.12.927.17.1 rc17.1 rc27.1 rc37.1 rc4ae79c310b1a6f97429a5784b65f125d9cc9c95b1
Vendor states this is fixed in 67461e0c15335894cc5d3b84cda823bf8cbdc886 (fixed)
Vendor states this is fixed in 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a (fixed)
Vendor states this is fixed in 86d2b20644b11d21fe52c596e6e922b4590a3e3f (fixed)
Vendor states this is fixed in 9900f6954be779011e7c2cd42addd87baf028bc5 (fixed)
Vendor states this is fixed in f2a4827e980ba07de4391fa84d9c39a12726bdd7 (fixed)
Vendor states this is fixed in fb30a3890d62fd50a95aef684faf64a307592e42 (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.92 (unaffected)
Vendor states this is fixed in 6.18.34 (unaffected)
Vendor states this is fixed in 6.6.142 (unaffected)
Vendor states this is fixed in 7.0.11 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card