PT-2026-52234 · Linux · Linux
Published
2026-06-25
·
Updated
2026-06-25
·
CVE-2026-53138
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Bound VBIOS record-chain walk loops
[Why & How]
All record-chain walk loops in bios parser.c and bios parser2.c use
for(;;) and only terminate on a 0xFF record type sentinel or zero
record size. A malformed VBIOS image missing the terminator record
causes unbounded iteration at probe time, potentially hundreds of
thousands of iterations with record size=1. In the final iterations
near the BIOS image boundary, struct casts beyond the 2-byte header
validated by GET IMAGE can also read out of bounds.
Cap all 14 record-chain walk loops to BIOS MAX NUM RECORD (256)
iterations. The atombios.h defines up to 22 distinct record types
and atomfirmware.h has 13. Assuming an average of less than 10
records per type (which is reasonable since most are connector-
based) 256 is a generous upper bound.
(cherry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93)
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux