LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52485: drm/amd/display: Wake DMCUB before sending a command

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Wake DMCUB before sending a command [Why] We can hang in place trying to send commands when the DMCUB isn't powered on. [How] For functions that execute within a DC context or DC lock we can wrap the direct calls to dm_execute_dmub_cmd/list with code that exits idle power optimizations and reallows once we're done with the command submission on success. For DM direct submissions the DM will need to manage the enter/exit sequencing manually. We cannot invoke a DMCUB command directly within the DM execution helper or we can deadlock.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause systems using the AMD display stack to hang when the display microcontroller is asleep and a command is sent. The public record does not provide CVSS, CWE, or exploitation evidence, so business risk is uncertain but appears centered on availability rather than data theft.

Executive priority

Treat this as a stability and operational resilience issue until vendor scoring clarifies severity. Patch through normal kernel maintenance, prioritizing workstations, GPU-enabled Linux systems, and any operational endpoints where display stack hangs would disrupt service.

Technical view

In drm/amd/display, command submission could occur while DMCUB was not powered on, causing a hang. The fix wakes or exits idle power optimizations around direct dm_execute_dmub_cmd/list submissions in DC contexts, while avoiding direct DMCUB commands inside the execution helper to prevent deadlock.

Likely exposure

Exposure is limited to Linux kernels using the AMD display driver paths described by the kernel fix. The source lists Linux as affected but does not identify distributions, hardware models, cloud images, or precise packaged kernel versions.

Exploitation context

No KEV listing is present, and the provided sources do not claim active exploitation or public exploit availability. The described failure mode is a local kernel/display hang condition tied to DMCUB power state and command submission timing.

Researcher notes

The evidence is sparse: no CVSS, CWE, exploit note, or distribution matrix is provided. Analysis should stay close to the kernel commit rationale: DMCUB idle power state handling around command submission and deadlock avoidance in execution helper paths.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Use distribution advisories to map the fix to packaged kernel versions.
  • For custom kernels, backport the referenced stable commits after validation.
  • Prioritize systems using AMD display hardware or drm/amd/display.
  • If patch timing is unclear, check vendor kernel guidance before deploying changes.

Validation and detection

  • Inventory Linux kernel versions on systems with AMD display hardware.
  • Check whether referenced stable commit fixes are present in deployed kernels.
  • Review distribution changelogs for CVE-2023-52485 or matching drm/amd/display patches.
  • Test display suspend, resume, and power-management workflows after updating.
  • Confirm monitoring covers kernel hangs or GPU/display driver lockups.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52485 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7cunaffected
LinuxLinux4.15, 0, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.