Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-52625 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

drm/amd/display: Refactor DMCUB enter/exit idle interface

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2023-52625 is recorded against 2 packages.

  • kernel (from 4.15.0 up to 6.7.3)
  • linux-kernel (fixed in 6.7.3)

Timeline and source

Published on 26 March 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-03-26
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 4.15.0 6.7.3
linux-kernel — 6.7.3

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2023-52625 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2023
✓