Skip to content
Noroxi
CVE-2026-53136· NVD / CVE Program· CNA Linux

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size

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)

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Jul 7, 2026
EPSS
0.1% · 2th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Affected systems

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.15 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.94
  • linux linux kernel6.13 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.15affected
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before 029571d51140650783be4fb98fe7cb4754752086affected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before 5f8b39452fb16f507c9e4d8b4a83ce27e893307caffected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before 4d1c3c26c2ab1842e139e61983395d64bd2e518baffected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before d6be8e59af412623e3d874be3a048406c0edfe60affected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before 3f32d52ec604c659725d865cf8cc6a17a33f9c6aaffected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before 8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117affected · git
    • 1e8635ea0ea370bf4f0f2b2f1b3eb61474dd962a and later · before fb0707ce00eef4e2d60c3020e1c0432739703e4aaffected · git
    • before 4.15not affected · semver
    • 5.15.210 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.49.1.el10_26.12.0-211.49.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux029571d51140650783be4fb98fe7cb4754752086Vendor (CNA)
Linux Linux3f32d52ec604c659725d865cf8cc6a17a33f9c6aVendor (CNA)
Linux Linux4d1c3c26c2ab1842e139e61983395d64bd2e518bVendor (CNA)
Linux Linux5f8b39452fb16f507c9e4d8b4a83ce27e893307cVendor (CNA)
Linux Linux8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117Vendor (CNA)
Linux Linuxd6be8e59af412623e3d874be3a048406c0edfe60Vendor (CNA)
Linux Linuxfb0707ce00eef4e2d60c3020e1c0432739703e4aVendor (CNA)
almalinux:bpftool4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records