CVE-2026-53138
Last modified
CVE-2026-53138 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.15, < 5.10.260 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.211 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.177 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.144 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53138?
How severe is CVE-2026-53138?
How do I fix CVE-2026-53138?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53132In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53133In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53134In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53135In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53136In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53137In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53139In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5314A vulnerability was found in Nothings stb up to 1.26. Impact…8.8
- CVE-2026-53140In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53141In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53142In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53143In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53138?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
