CVE-2026-64097 Details
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)
A vulnerability in the Linux kernel's AMD display driver allows for out-of-bounds reads due to improper validation of GPIO pin lookup table sizes. The issue arises in the BIOS parsers that handle GPIO information, where the element count is derived from a VBIOS header field. If the reported size exceeds the actual data mapped in the BIOS image, the parser can read past the image's end, leading to an out-of-bounds access. This vulnerability affects several versions of the Linux kernel.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for upgrading the kernel can be found in the official Linux kernel documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/67461e0c15335894cc5d3b84cda823bf8cbdc886 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7ca695b3122297b06a3ed605bbe1cd32c85d9f5a | kernel.org | Patch |
| https://git.kernel.org/stable/c/86d2b20644b11d21fe52c596e6e922b4590a3e3f | kernel.org | Patch |
| https://git.kernel.org/stable/c/9900f6954be779011e7c2cd42addd87baf028bc5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f2a4827e980ba07de4391fa84d9c39a12726bdd7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/fb30a3890d62fd50a95aef684faf64a307592e42 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.15, < 6.1.175 >= 6.2, < 6.6.142 >= 6.7, < 6.12.92 >= 6.13, < 6.18.34 >= 6.19, < 7.0.11 7.1 rc1 7.1 rc2 7.1 rc3 7.1 rc4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 11, 2026 | Initial Analysis | [email protected] |
| Jul 20, 2026 | CVE Modified | kernel.org |
| Jul 20, 2026 | CVE Modified | kernel.org |
| Jul 19, 2026 | New CVE Received | kernel.org |