CVE-2026-53136

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (7)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fb0707ce00eef4e2d60c3020e1c0432739703e4a
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d6be8e59af412623e3d874be3a048406c0edfe60
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8aaa7e317fbd4beb9c6a9f77aa4cf52fae78b117
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f8b39452fb16f507c9e4d8b4a83ce27e893307c
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d1c3c26c2ab1842e139e61983395d64bd2e518b
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f32d52ec604c659725d865cf8cc6a17a33f9c6a
generic

drm/amd/display: Clamp VBIOS HDMI retimer register count to array size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/029571d51140650783be4fb98fe7cb4754752086

Vendor Advisories for CVE-2026-53136(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 229 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:40 UTCEG score recompute
  3. 2026-09-18 07:40 UTCVendor advisory
  4. 2026-09-18 07:40 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 01:28 UTCEG score recompute
  8. 2026-09-14 01:28 UTCVendor advisory
  9. 2026-09-14 01:28 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 09:45 UTCVendor advisory
  12. 2026-09-13 09:45 UTCGHSA enrichment
  13. 2026-09-12 16:01 UTCEG score recompute
  14. 2026-09-12 16:01 UTCVendor advisory
  15. 2026-09-12 16:01 UTCGHSA enrichment
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-30 19:45 UTCEG score recompute
  24. 2026-08-30 19:45 UTCVendor advisory
  25. 2026-08-30 19:44 UTCGHSA enrichment
Show 75 more
  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 02:56 UTCEG score recompute
  5. 2026-08-28 02:56 UTCVendor advisory
  6. 2026-08-28 02:56 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 00:13 UTCEG score recompute
  11. 2026-08-25 00:13 UTCVendor advisory
  12. 2026-08-25 00:13 UTCGHSA enrichment
  13. 2026-08-24 13:17 UTCEG score recompute
  14. 2026-08-24 13:17 UTCVendor advisory
  15. 2026-08-24 13:17 UTCGHSA enrichment
  16. 2026-08-23 20:25 UTCVendor advisory
  17. 2026-08-23 20:25 UTCGHSA enrichment
  18. 2026-08-23 09:29 UTCEG score recompute
  19. 2026-08-23 09:29 UTCVendor advisory
  20. 2026-08-23 09:29 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 22:34 UTCVendor advisory
  23. 2026-08-22 22:34 UTCGHSA enrichment
  24. 2026-08-22 10:56 UTCEG score recompute
  25. 2026-08-22 10:56 UTCVendor advisory
  26. 2026-08-22 10:56 UTCGHSA enrichment
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 17:27 UTCVendor advisory
  29. 2026-08-21 17:27 UTCGHSA enrichment
  30. 2026-08-21 05:11 UTCEG score recompute
  31. 2026-08-21 05:11 UTCVendor advisory
  32. 2026-08-21 05:11 UTCGHSA enrichment
  33. 2026-08-20 22:55 UTCEPSS rescore
  34. 2026-08-20 18:14 UTCVendor advisory
  35. 2026-08-20 18:14 UTCGHSA enrichment
  36. 2026-08-20 07:11 UTCEG score recompute
  37. 2026-08-20 07:11 UTCVendor advisory
  38. 2026-08-20 07:11 UTCGHSA enrichment
  39. 2026-08-19 17:04 UTCEPSS rescore
  40. 2026-08-19 12:40 UTCVendor advisory
  41. 2026-08-19 12:40 UTCGHSA enrichment
  42. 2026-08-19 01:35 UTCEG score recompute
  43. 2026-08-19 01:35 UTCVendor advisory
  44. 2026-08-19 01:35 UTCGHSA enrichment
  45. 2026-08-18 13:48 UTCEPSS rescore
  46. 2026-08-17 17:08 UTCEG score recompute
  47. 2026-08-17 17:08 UTCGHSA enrichment
  48. 2026-08-17 13:47 UTCEPSS rescore
  49. 2026-08-17 06:11 UTCGHSA enrichment
  50. 2026-08-16 18:27 UTCEG score recompute
  51. 2026-08-16 18:27 UTCGHSA enrichment
  52. 2026-08-16 14:56 UTCEPSS rescore
  53. 2026-08-16 06:33 UTCEG score recompute
  54. 2026-08-16 06:33 UTCGHSA enrichment
  55. 2026-08-16 02:14 UTCEPSS rescore
  56. 2026-08-15 19:37 UTCGHSA enrichment
  57. 2026-08-15 08:36 UTCEG score recompute
  58. 2026-08-15 08:36 UTCGHSA enrichment
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 19:53 UTCGHSA enrichment
  61. 2026-08-14 08:57 UTCGHSA enrichment
  62. 2026-08-13 22:01 UTCEG score recompute
  63. 2026-08-13 22:01 UTCGHSA enrichment
  64. 2026-08-13 22:00 UTCEPSS rescore
  65. 2026-08-13 11:05 UTCGHSA enrichment
  66. 2026-08-13 00:10 UTCEG score recompute
  67. 2026-08-13 00:10 UTCGHSA enrichment
  68. 2026-08-12 13:51 UTCEPSS rescore
  69. 2026-08-12 13:14 UTCGHSA enrichment
  70. 2026-08-12 02:18 UTCGHSA enrichment
  71. 2026-08-11 15:23 UTCEG score recompute
  72. 2026-08-11 15:22 UTCGHSA enrichment
  73. 2026-08-11 04:26 UTCEG score recompute
  74. 2026-08-11 04:26 UTCGHSA enrichment
  75. 2026-08-11 00:00 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53136?
CVE-2026-53136 is a high vulnerability published on June 25, 2026. 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 (v111 and v21) contain HdmiRegNum and Hdmi6GRegNum fields that are used as loop bounds when copying retimer I2C…
When was CVE-2026-53136 disclosed?
CVE-2026-53136 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53136 actively exploited?
CVE-2026-53136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53136?
CVE-2026-53136 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53136?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53136, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53136

Explore →

Is Your Infrastructure Affected by CVE-2026-53136?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs