CVE-2026-53138
What it is
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)
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.260
- Linux Kernel < 5.15.211
- Linux Kernel < 6.1.177
- Linux Kernel < 6.6.144
- Linux Kernel < 6.12.94
- Linux Kernel < 6.18.36
- Linux Kernel < 7.0.13
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53138.md and follow it. Check whether this project is affected by CVE-2026-53138. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/04e271a952b8863bbafc99bd51aca4c32bff0e0d
- https://git.kernel.org/stable/c/0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1
- https://git.kernel.org/stable/c/2645e3caf7e013189da9c6ff621d006cca5a538b
- https://git.kernel.org/stable/c/499c6b43a79dd684bddbd18fe8b2235aa2764db4
- https://git.kernel.org/stable/c/6173cfea2f916e01c4f98e29cd654384a05e32a3
- https://git.kernel.org/stable/c/6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56
- https://git.kernel.org/stable/c/e94f5323c41f32a74160378c3b19850d1f203ad5
- https://git.kernel.org/stable/c/ff287df16a1a58aca78b08d1f3ee09fc44da0351
References
- https://git.kernel.org/stable/c/04e271a952b8863bbafc99bd51aca4c32bff0e0d
- https://git.kernel.org/stable/c/0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1
- https://git.kernel.org/stable/c/2645e3caf7e013189da9c6ff621d006cca5a538b
- https://git.kernel.org/stable/c/499c6b43a79dd684bddbd18fe8b2235aa2764db4
- https://git.kernel.org/stable/c/6173cfea2f916e01c4f98e29cd654384a05e32a3
- https://git.kernel.org/stable/c/6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56
- https://git.kernel.org/stable/c/e94f5323c41f32a74160378c3b19850d1f203ad5
- https://git.kernel.org/stable/c/ff287df16a1a58aca78b08d1f3ee09fc44da0351