Vulnerability · Published Jul 19, 2026 · Assigned by Linux
CVE-2026-64097drm/amd/display: Validate GPIO pin LUT table size before iterating
High 7.8
In plain English
A high-severity out-of-bounds read in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.176-1 | DEBIAN-CVE-2026-64097 |
| Debian:13 | linux | 6.12.94-1 | DEBIAN-CVE-2026-64097 |
| Debian:14 | linux | 7.0.12-1 | DEBIAN-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux | 7.0.0-28.28 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | USN-8729-6 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1009.9 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | USN-8729-6 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | USN-8761-1 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | USN-8761-3 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1065.72 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1065.72~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1008.8 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | USN-8729-3 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1003.4 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1010.10 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1066.67~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1016.16 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | USN-8729-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2016.16 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1035.38 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1009.9 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | USN-8802-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1008.8 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | USN-8802-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1015.15 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-139.139~22.04.1 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-28.28.1~24.04.3 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-64097 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | UBUNTU-CVE-2026-64097 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2026-64097 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before 9900f6954be779011e7c2cd42addd87baf028bc5ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before fb30a3890d62fd50a95aef684faf64a307592e42ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before 67461e0c15335894cc5d3b84cda823bf8cbdc886ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before 7ca695b3122297b06a3ed605bbe1cd32c85d9f5aae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before f2a4827e980ba07de4391fa84d9c39a12726bdd7ae79c310b1a6f97429a5784b65f125d9cc9c95b1 – before 86d2b20644b11d21fe52c596e6e922b4590a3e3f |
| Linux | Linux | 4.15 |
Weakness: CWE-125 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/9900f6954be779011e7c2cd42addd87baf028bc5
- https://git.kernel.org/stable/c/fb30a3890d62fd50a95aef684faf64a307592e42
- https://git.kernel.org/stable/c/67461e0c15335894cc5d3b84cda823bf8cbdc886
- https://git.kernel.org/stable/c/7ca695b3122297b06a3ed605bbe1cd32c85d9f5a
- https://git.kernel.org/stable/c/f2a4827e980ba07de4391fa84d9c39a12726bdd7
- https://git.kernel.org/stable/c/86d2b20644b11d21fe52c596e6e922b4590a3e3f