Answer in brief
CVE-2026-64097 records a Unknown severity vulnerability in drm/amd/display: Validate GPIO pin LUT table size before iterating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <9900f6954be779011e7c2cd42addd87baf028bc5 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <fb30a3890d62fd50a95aef684faf64a307592e42 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <67461e0c15335894cc5d3b84cda823bf8cbdc886 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <7ca695b3122297b06a3ed605bbe1cd32c85d9f5a || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <f2a4827e980ba07de4391fa84d9c39a12726bdd7 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <86d2b20644b11d21fe52c596e6e922b4590a3e3f | 9900f6954be779011e7c2cd42addd87baf028bc5, fb30a3890d62fd50a95aef684faf64a307592e42, 67461e0c15335894cc5d3b84cda823bf8cbdc886, 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a, f2a4827e980ba07de4391fa84d9c39a12726bdd7, 86d2b20644b11d21fe52c596e6e922b4590a3e3f |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64097 records a Unknown severity vulnerability in drm/amd/display: Validate GPIO pin LUT table size before iterating. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <9900f6954be779011e7c2cd42addd87baf028bc5 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <fb30a3890d62fd50a95aef684faf64a307592e42 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <67461e0c15335894cc5d3b84cda823bf8cbdc886 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <7ca695b3122297b06a3ed605bbe1cd32c85d9f5a || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <f2a4827e980ba07de4391fa84d9c39a12726bdd7 || >=ae79c310b1a6f97429a5784b65f125d9cc9c95b1 <86d2b20644b11d21fe52c596e6e922b4590a3e3f | 9900f6954be779011e7c2cd42addd87baf028bc5, fb30a3890d62fd50a95aef684faf64a307592e42, 67461e0c15335894cc5d3b84cda823bf8cbdc886, 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a, f2a4827e980ba07de4391fa84d9c39a12726bdd7, 86d2b20644b11d21fe52c596e6e922b4590a3e3f |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.