CVE-2026-53138

/// Technical description

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)

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References