High 7.1Published Jun 25, 2026

CVE-2026-53138drm/amd/display: Bound VBIOS record-chain walk loops

Updated under an hour ago (Oct 26, 2026, 5:00 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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)

CVSS: 7.1 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Jul 4, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c before e94f5323c41f32a74160378c3b19850d1f203ad5; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c builds before 04e271a952b8863bbafc99bd51aca4c32bff0e0d; from 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c before 6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c builds before 499c6b43a79dd684bddbd18fe8b2235aa2764db4; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c builds before 6173cfea2f916e01c4f98e29cd654384a05e32a3; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c builds before 0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1; 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c builds before 2645e3caf7e013189da9c6ff621d006cca5a538b; from 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c before ff287df16a1a58aca78b08d1f3ee09fc44da0351	CNA record
linux linux_kernel linux:linux_kernel	from 4.15 before 5.10.260; from 5.11 before 5.15.211; from 5.16 before 6.1.177; from 6.2 before 6.6.144; from 6.7 before 6.12.94; from 6.13 before 6.18.36; from 6.19 before 7.0.13; 7.1; and 5 more ranges	NVD

References

References

https://git.kernel.org/stable/c/e94f5323c41f32a74160378c3b19850d1f203ad5	patch
https://git.kernel.org/stable/c/04e271a952b8863bbafc99bd51aca4c32bff0e0d	patch
https://git.kernel.org/stable/c/6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56	patch
https://git.kernel.org/stable/c/499c6b43a79dd684bddbd18fe8b2235aa2764db4	patch
https://git.kernel.org/stable/c/6173cfea2f916e01c4f98e29cd654384a05e32a3	patch
https://git.kernel.org/stable/c/0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1	patch
https://git.kernel.org/stable/c/2645e3caf7e013189da9c6ff621d006cca5a538b	patch
https://git.kernel.org/stable/c/ff287df16a1a58aca78b08d1f3ee09fc44da0351	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.