drm/amd/display: Validate GPIO pin LUT table size before iterating
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae79c310b1a6f97429a5784b65f125d9cc9c95b1 · < 86d2b20644b11d21fe52c596e6e922b4590a3e3f| No fix yet |
| Linux Linux |
|
|
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)
From the CVE record · Linux
The AMD display GPIO pin parsers in the Linux kernel do not validate that the full VBIOS GPIO pin table fits within the BIOS image. If a VBIOS table claims a size larger than the mapped data, parsing it can read past the end of the image; the input does not establish how an attacker could supply such a table.
Engineers running Linux kernels with AMD display support should check whether their kernel includes the fix; affected versions are not specified.