# CVE-2024-46870: drm/amd/display: Disable DMCUB timeout for DCN35

> A race condition in the AMD display driver can cause system hangs or undefined display states due to DMCUB timeout handling issues.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/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:** 9 Oct 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-50781, AZL-50906, BELL-CVE-2024-46870, DEBIAN-CVE-2024-46870, GHSA-r56q-rrpj-wqj3, ROOT-OS-DEBIAN-11-CVE-2024-46870, ROOT-OS-DEBIAN-12-CVE-2024-46870, ROOT-OS-UBUNTU-2204-CVE-2024-46870, UBUNTU-CVE-2024-46870

## What is CVE-2024-46870?

CVE-2024-46870 is a medium-severity vulnerability in Linux kernel, published on 9 Oct 2024. 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: Disable DMCUB timeout for DCN35

[Why]
DMCUB can intermittently take longer than expected to process commands.

Old ASIC policy was to continue while logging a diagnostic error - which
works fine for ASIC without IPS, but with IPS this could lead to a race
condition where we attempt to access DCN state while it's inaccessible,
leading to a system hang when the NIU port is not disabled or register
accesses that timeout and the display configuration in an undefined
state.

[How]
We need to investigate why these accesses take longer than expected, but
for now we should disable the timeout on DCN35 to avoid this race
condition. Since the waits happen only at lower interrupt levels the
risk of taking too long at higher IRQ and causing a system watchdog
timeout are minimal.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-46870?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-46870?

Apply the vendor's patch.

## Is CVE-2024-46870 being exploited?

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

What it is: CVE-2024-46870 is a medium-severity vulnerability in Linux kernel, published on 9 Oct 2024. 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-2024-46870 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-2024-46870/ (Markdown: https://insights.sbomify.com/CVE-2024-46870/index.md)
```

## Sources

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

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