Kernel heap corruption via unchecked VBIOS counts
Published Jun 25, 2026 · Updated Jun 25, 2026
Out-of-bounds write in Linux kernel AMD display parsing allows local users to corrupt kernel heap via malformed VBIOS retimer counts. HdmiRegNum and Hdmi6GRegNum directly bound copy loops into 9-entry and 3-entry retimer-setting arrays without validation. The write occurs only when AMD display-driver probe parses a malformed integrated VBIOS table; published evidence establishes heap corruption, not a specific post-corruption outcome.
Summary
What happened
Out-of-bounds write in Linux kernel AMD display parsing allows local users to corrupt kernel heap via malformed VBIOS retimer counts. HdmiRegNum and Hdmi6GRegNum directly bound copy loops into 9-entry and 3-entry retimer-setting arrays without validation. The write occurs only when AMD display-driver probe parses a malformed integrated VBIOS table; published evidence establishes heap corruption, not a specific post-corruption outcome.
The record
- CVE
- CVE-2026-53136
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.15.210
- Affected versionversion=0 <6.1.176
- Affected versionversion=0 <6.12.94
- Affected versionversion=0 <6.18.36
- Affected versionversion=0 <6.6.143
- Affected versionversion=0 <7.0.13
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <029571d51140650783be4fb98fe7cb4754752086
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3f32d52ec604c659725d865cf8cc6a17a33f9c6a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4d1c3c26c2ab1842e139e61983395d64bd2e518b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5f8b39452fb16f507c9e4d8b4a83ce27e893307c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d6be8e59af412623e3d874be3a048406c0edfe60
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb0707ce00eef4e2d60c3020e1c0432739703e4a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo