CVE-2026-53136
Last modified
CVE-2026-53136 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size [Why & How] The VBIOS integrated info tables (v1_11 and v2_1) contain HdmiRegNum and Hdmi6GRegNum fields that are used as loop bounds when copying retimer I2C register settings into fixed-size arrays (dp*_ext_hdmi_reg_settings[9] and dp*_ext_hdmi_6g_reg_settings[3]). These u8 fields are not validated before use, so a malformed VBIOS can specify values up to 255, causing an out-of-bounds heap write during driver probe. Clamp each register count to the destination array size using min_t() before the copy loops, in both get_integrated_info_v11() and get_integrated_info_v2_1(). (cherry picked from commit 5a7f0ef90195940c54b0f5bb85b87da55f038c69). EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Clamp VBIOS HDMI retimer register count to array size [Why & How] The VBIOS integrated info tables (v1_11 and v2_1) contain HdmiRegNum and Hdmi6GRegNum fields that are used as loop bounds when copying retimer I2C register settings into fixed-size arrays (dp*_ext_hdmi_reg_settings[9] and dp*_ext_hdmi_6g_reg_settings[3]). These u8 fields are not validated before use, so a malformed VBIOS can specify values up to 255, causing an out-of-bounds heap write during driver probe. Clamp each register count to the destination array size using min_t() before the copy loops, in both get_integrated_info_v11() and get_integrated_info_v2_1(). (cherry picked from commit 5a7f0ef90195940c54b0f5bb85b87da55f038c69)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.15, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| 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-53136?
How severe is CVE-2026-53136?
How do I fix CVE-2026-53136?
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-53130In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53131In the Linux kernel, the following vulnerability has been re…9.4
- 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-53137In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53138In the Linux kernel, the following vulnerability has been re…7.1
- 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
Are you affected by CVE-2026-53136?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
