# CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in dp_get_eq_aux_rd_interval()

> An out-of-bounds read in the AMD display driver allows attackers to disclose memory or cause a denial of service via crafted DP repeater counts.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 1 Jul 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-91620, BELL-CVE-2026-53330, DEBIAN-CVE-2026-53330, GHSA-x86r-325j-5wq6, ROOT-OS-DEBIAN-11-CVE-2026-53330, ROOT-OS-DEBIAN-12-CVE-2026-53330, ROOT-OS-DEBIAN-13-CVE-2026-53330, ROOT-OS-UBUNTU-2204-CVE-2026-53330, ROOT-OS-UBUNTU-2404-CVE-2026-53330, UBUNTU-CVE-2026-53330

## What is CVE-2026-53330?

CVE-2026-53330 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 Jul 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: Fix out-of-bounds read in dp_get_eq_aux_rd_interval()

[Why & How]
The aux_rd_interval array in struct dc_lttpr_caps is declared with
MAX_REPEATER_CNT - 1 (7) elements, indexed 0..6. However, the offset
parameter passed to dp_get_eq_aux_rd_interval() can be as large as
MAX_REPEATER_CNT (8) when a sink reports 8 LTTPR repeaters via DPCD.
This leads to an out-of-bounds read of aux_rd_interval[7] when offset
is 8.

Fix this by growing aux_rd_interval to MAX_REPEATER_CNT elements to
accommodate the full range of valid repeater counts defined by the DP
spec.

(cherry picked from commit a55a458a8df37a65ffda5cf721d554a8f74f6b04)

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53330 being exploited?

There is no known exploitation of CVE-2026-53330 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-53330 and fix it if it is affected.

What it is: CVE-2026-53330 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 Jul 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-53330 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-53330/ (Markdown: https://insights.sbomify.com/CVE-2026-53330/index.md)
```

## Sources

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

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