VulnerabilityPublished 25 Jun 2026Updated 6 Nov 2026

CVE-2026-53136: Linux kernel · drm/amd/display: Clamp VBIOS HDMI retimer register count to array size

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in fb0707ce00eef4e2d60c3020e1c0432739703e4a : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in fb0707ce00eef4e2d60c3020e1c0432739703e4a, d6be8e59af412623e3d874be3a048406c0edfe60, 029571d51140650783be4fb98fe7cb4754752086 +4

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < fb0707ce00eef4e2d60c3020e1c0432739703e4a	Fixed in fb0707ce00eef4e2d60c3020e1c0432739703e4a
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < d6be8e59af412623e3d874be3a048406c0edfe60	Fixed in d6be8e59af412623e3d874be3a048406c0edfe60
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < 029571d51140650783be4fb98fe7cb4754752086	Fixed in 029571d51140650783be4fb98fe7cb4754752086
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < 8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117	Fixed in 8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < 5f8b39452fb16f507c9e4d8b4a83ce27e893307c	Fixed in 5f8b39452fb16f507c9e4d8b4a83ce27e893307c
LinuxLinux	Affected ≥ 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a, < 4d1c3c26c2ab1842e139e61983395d64bd2e518b	Fixed in 4d1c3c26c2ab1842e139e61983395d64bd2e518b

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)

References

Community reviews

Loading reviews…