# CVE-2023-52625: drm/amd/display: Refactor DMCUB enter/exit idle interface

> A flaw in the Linux kernel's AMD display driver can cause a system hang when sending commands to the DMCUB while it is powered off.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/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:** 26 Mar 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-52625, DEBIAN-CVE-2023-52625, GHSA-78r6-645f-335q, ROOT-OS-DEBIAN-11-CVE-2023-52625, ROOT-OS-DEBIAN-12-CVE-2023-52625, ROOT-OS-UBUNTU-2204-CVE-2023-52625, UBUNTU-CVE-2023-52625

## What is CVE-2023-52625?

CVE-2023-52625 is a medium-severity denial of service vulnerability in Linux kernel, published on 26 Mar 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: Refactor DMCUB enter/exit idle interface

[Why]
We can hang in place trying to send commands when the DMCUB isn't
powered on.

[How]
We need to exit out of the idle state prior to sending a command,
but the process that performs the exit also invokes a command itself.

Fixing this issue involves the following:

1. Using a software state to track whether or not we need to start
   the process to exit idle or notify idle.

It's possible for the hardware to have exited an idle state without
driver knowledge, but entering one is always restricted to a driver
allow - which makes the SW state vs HW state mismatch issue purely one
of optimization, which should seldomly be hit, if at all.

2. Refactor any instances of exit/notify idle to use a single wrapper
   that maintains this SW state.

This works simialr to dc_allow_idle_optimizations, but works at the
DMCUB level and makes sure the state is marked prior to any notify/exit
idle so we don't enter an infinite loop.

3. Make sure we exit out of idle prior to sending any commands or
   waiting for DMCUB idle.

This patch takes care of 1/2. A future patch will take care of wrapping
DMCUB command submission with calls to this new interface.

## Which versions are affected by CVE-2023-52625?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52625?

Apply the vendor's patch.

## Is CVE-2023-52625 being exploited?

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

What it is: CVE-2023-52625 is a medium-severity denial of service vulnerability in Linux kernel, published on 26 Mar 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-2023-52625 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-2023-52625/ (Markdown: https://insights.sbomify.com/CVE-2023-52625/index.md)
```

## Sources

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

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