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

> A malicious HDMI repeater can trigger an out-of-bounds write in the Linux kernel's AMD display driver, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** AZL-90575, BELL-CVE-2026-53137, DEBIAN-CVE-2026-53137, GHSA-36gr-gw56-g35v, ROOT-OS-DEBIAN-11-CVE-2026-53137, ROOT-OS-DEBIAN-12-CVE-2026-53137, ROOT-OS-UBUNTU-2204-CVE-2026-53137, ROOT-OS-UBUNTU-2404-CVE-2026-53137, UBUNTU-CVE-2026-53137

## What is CVE-2026-53137?

CVE-2026-53137 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-53137?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53137?

Apply the vendor's patch.

## Is CVE-2026-53137 being exploited?

There is no known exploitation of CVE-2026-53137 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53137 and fix it if it is affected.

What it is: CVE-2026-53137 is a high-severity memory corruption vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53137 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53137/ (Markdown: https://insights.sbomify.com/CVE-2026-53137/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53137
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53137
- OSV: https://osv.dev/vulnerability/CVE-2026-53137

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53137/
Summaries are generated and may contain mistakes; the official description above is the record.