Skip to main content
VulnerabilityPublished Updated

CVE-2026-53137: Linux kernel · drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f0f3981c43b32cadfe373d636d9e9ca522bb3702 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f0f3981c43b32cadfe373d636d9e9ca522bb3702, bfba882cfcd08f6540f72f48e786b6404f5d2c5b, 1906064d50d194a145486e5caf3db3e708b6f6ef +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < f0f3981c43b32cadfe373d636d9e9ca522bb3702
Fixed in
  • f0f3981c43b32cadfe373d636d9e9ca522bb3702
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < bfba882cfcd08f6540f72f48e786b6404f5d2c5b
Fixed in
  • bfba882cfcd08f6540f72f48e786b6404f5d2c5b
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < 1906064d50d194a145486e5caf3db3e708b6f6ef
Fixed in
  • 1906064d50d194a145486e5caf3db3e708b6f6ef
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < 964e50ef7b8f09815a7d05b8326af700f8d5bc96
Fixed in
  • 964e50ef7b8f09815a7d05b8326af700f8d5bc96
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < 98cfb7530ea91d8e5e928285cdce58e1131f6e83
Fixed in
  • 98cfb7530ea91d8e5e928285cdce58e1131f6e83
LinuxLinuxAffected
  • ≥ eff682f83c9c2030761e7536c5d97e1b20f71c15, < 91fb41218c413989d8b6c837748751454b452d68
Fixed in
  • 91fb41218c413989d8b6c837748751454b452d68

Description

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)

References

Community reviews

Loading reviews…