In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The… (CVE-2026-64097)
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)
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's drm/amd/display component involved improper validation of the GPIO pin LUT table size derived from the VBIOS table_header.structuresize field. The functions get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() used this size to iterate over gpio_pin[] entries without confirming the entire claimed structure was within the BIOS image. This could cause an out-of-bounds read if the VBIOS reported a structuresize larger than the actual mapped data. The issue was fixed by adding a call to bios_get_image() to validate the full structuresize is accessible before iteration, preventing out-of-bounds memory access.
Potential Impact
The vulnerability allows an out-of-bounds read in the Linux kernel when parsing the GPIO pin LUT table from the VBIOS. This could potentially lead to information disclosure or kernel instability. No known exploits in the wild have been reported. The impact is limited to the Linux kernel's AMD display driver handling of VBIOS data.
Mitigation Recommendations
A fix has been applied in the Linux kernel to validate the full GPIO pin LUT table size before iterating, preventing out-of-bounds reads. Users should update to the Linux kernel version containing this fix. Since this is not a cloud service, remediation depends on applying the official kernel update. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The… (CVE-2026-64097)
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)
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's drm/amd/display component involved improper validation of the GPIO pin LUT table size derived from the VBIOS table_header.structuresize field. The functions get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() used this size to iterate over gpio_pin[] entries without confirming the entire claimed structure was within the BIOS image. This could cause an out-of-bounds read if the VBIOS reported a structuresize larger than the actual mapped data. The issue was fixed by adding a call to bios_get_image() to validate the full structuresize is accessible before iteration, preventing out-of-bounds memory access.
Potential Impact
The vulnerability allows an out-of-bounds read in the Linux kernel when parsing the GPIO pin LUT table from the VBIOS. This could potentially lead to information disclosure or kernel instability. No known exploits in the wild have been reported. The impact is limited to the Linux kernel's AMD display driver handling of VBIOS data.
Mitigation Recommendations
A fix has been applied in the Linux kernel to validate the full GPIO pin LUT table size before iterating, preventing out-of-bounds reads. Users should update to the Linux kernel version containing this fix. Since this is not a cloud service, remediation depends on applying the official kernel update. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-78vx-v25w-4237
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64097"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912b8c4
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:49:24 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.