CVE-2026-53137

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size

[Why & How] During HDCP 2.x repeater authentication over HDMI, the driver reads the sink's RxStatus register and extracts a 10-bit message size field (max value 1023). This value is used as the read length for the ReceiverID list without being clamped to the size of the destination buffer rx_id_list[177]. A malicious HDMI repeater could advertise a message size larger than the buffer, causing an out-of-bounds write during the I2C read.

Clamp the read length in mod_hdcp_read_rx_id_list() to the size of the rx_id_list buffer, matching the approach already used in the DP branch.

(cherry picked from commit 229212219e4247d9486f8ba41ef087358490be09)

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
10%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (8)

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

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98cfb7530ea91d8e5e928285cdce58e1131f6e83
generic

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/964e50ef7b8f09815a7d05b8326af700f8d5bc96
generic

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91fb41218c413989d8b6c837748751454b452d68
generic

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79e0273272a05fb26f9b1e55bf1a52eefc3b7b35
generic

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1906064d50d194a145486e5caf3db3e708b6f6ef

Vendor Advisories for CVE-2026-53137(2)

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

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
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.

Data Freshness Timeline

(refreshed 5× in last 7d / 85× 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 273 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53137?
CVE-2026-53137 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Clamp HDMI HDCP2 rxidlist read to buffer size [Why & How] During HDCP 2.x repeater authentication over HDMI, the driver reads the sink's RxStatus register and extracts a 10-bit message size field (max value 1023).…
When was CVE-2026-53137 disclosed?
CVE-2026-53137 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-53137 actively exploited?
CVE-2026-53137 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 90.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53137?
CVE-2026-53137 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53137, 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-53137

Explore →

Is Your Infrastructure Affected by CVE-2026-53137?

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

Start Free Scan →Browse All CVEs