Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-53136

7.8 · HIGH

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…

Published Jun 25, 2026CWE-787EPSS 0.13%

Overview

CVE-2026-53136 is a high-severity vulnerability. It was published on June 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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)

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/029571d51140650783be4fb98fe7cb4754752086Refgit.kernel.org/stable/c/3f32d52ec604c659725d865cf8cc6a17a33f9c6aRefgit.kernel.org/stable/c/4d1c3c26c2ab1842e139e61983395d64bd2e518bRefgit.kernel.org/stable/c/5f8b39452fb16f507c9e4d8b4a83ce27e893307cRefgit.kernel.org/stable/c/8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117Refgit.kernel.org/stable/c/d6be8e59af412623e3d874be3a048406c0edfe60Refgit.kernel.org/stable/c/fb0707ce00eef4e2d60c3020e1c0432739703e4a

How CyberStrike helps

Frequently asked questions

What is CVE-2026-53136?

CVE-2026-53136 is a high-severity vulnerability. It was published on June 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-53136?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53136?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53136?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53136 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999