drm/amd/display: Validate GPIO pin LUT table size before iterating
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)
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.175, 6.12.92, 6.18.34, 6.6.142, 7.0.11
- CVEs
- CVE-2026-64097
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 06:11 UTC · Revision 1
Source evidence
drm/amd/display: Validate GPIO pin LUT table size before iterating
core-osv · Original sourcePublished 19 Jul 2026, 15:40 UTC
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)
osv:CVE-2026-64097
Kernel
Fixed versions: 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11
Complete source record
{
"id": "b6318fc16882484cd803613de63b4ef33d22d096f51eb6d4ea07f081fa5db303",
"url": "https://osv.dev/vulnerability/CVE-2026-64097",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/amd/display: Validate GPIO pin LUT table size before iterating",
"summary": "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)",
"evidence": "osv:CVE-2026-64097",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.175",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.142",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.92",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.34",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.11",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-64097",
"aliases": [
"CVE-2026-64097"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ae79c310b1a6f97429a5784b65f125d9cc9c95b1"
},
{
"fixed": "9900f6954be779011e7c2cd42addd87baf028bc5"
},
{
"fixed": "fb30a3890d62fd50a95aef684faf64a307592e42"
},
{
"fixed": "67461e0c15335894cc5d3b84cda823bf8cbdc886"
},
{
"fixed": "7ca695b3122297b06a3ed605bbe1cd32c85d9f5a"
},
{
"fixed": "f2a4827e980ba07de4391fa84d9c39a12726bdd7"
},
{
"fixed": "86d2b20644b11d21fe52c596e6e922b4590a3e3f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64097.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "6.1.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.142"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.92"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.34"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.11"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64097.json"
}
}
],
"modified": "2026-10-28T02:30:42.987416399Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/67461e0c15335894cc5d3b84cda823bf8cbdc886",
"https://git.kernel.org/stable/c/7ca695b3122297b06a3ed605bbe1cd32c85d9f5a",
"https://git.kernel.org/stable/c/86d2b20644b11d21fe52c596e6e922b4590a3e3f",
"https://git.kernel.org/stable/c/9900f6954be779011e7c2cd42addd87baf028bc5",
"https://git.kernel.org/stable/c/f2a4827e980ba07de4391fa84d9c39a12726bdd7",
"https://git.kernel.org/stable/c/fb30a3890d62fd50a95aef684faf64a307592e42",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64097.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64097",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64097.json"
}
},
"related_cves": [
{
"value": "CVE-2026-64097",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 511004,
"published_at": "2026-07-19T15:40:03.599+00:00"
}