Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-53138

high

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 lo…

Vendor / product: Linux — linux kernel

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
7.1 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-06-25 09:16
Modified: 2026-11-06 17:18
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-06 17:46 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥4.15 <5.10.260, ≥5.11 <5.15.211, ≥5.16 <6.1.177, ≥6.2 <6.6.144, ≥6.7 <6.12.94, ≥6.13 <6.18.36

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

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

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-06 17:46 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs