LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53780: drm/amd/display: fix FCLK pstate change underflow

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix FCLK pstate change underflow [Why] Currently we set FCLK p-state change watermark calculated based on dummy p-state latency when UCLK p-state is not supported [How] Calculate FCLK p-state change watermark based on on FCLK pstate change latency in case UCLK p-state is not supported

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53780 is a Linux kernel AMD display driver flaw involving FCLK power-state watermark calculation. The public record says the issue is resolved, but gives no CVSS score, CWE, impact detail, or confirmed exploitation. Treat it as a kernel maintenance risk until your Linux vendor maps the fix into supported packages.

Executive priority

Track through normal kernel patch management unless your environment depends heavily on AMD graphics stability. There is insufficient evidence to justify emergency response, but kernel fixes should not be ignored.

Technical view

The fix changes AMD display logic so FCLK p-state change watermarks use FCLK p-state latency when UCLK p-state is unsupported. The source describes an underflow condition but does not specify confidentiality, integrity, availability impact, reachable attack paths, or required privileges.

Likely exposure

Exposure appears limited to Linux systems using affected kernel code paths in the AMD display driver. The bundle lists Linux kernel version markers and stable commit references, but not distribution package versions or full affected ranges.

Exploitation context

No provided source states active exploitation, public exploit availability, or KEV listing. The record is not in KEV. The practical exploitability and security impact are unclear from the available public bundle.

Researcher notes

The record lacks CVSS, CWE, exploit narrative, and concrete impact. Analysis should focus on the referenced commits and AMD display p-state watermark logic, while avoiding assumptions about privilege level or attack surface.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Check your distribution advisory for backported package names and fixed versions.
  • Prioritize systems using AMD GPUs or AMD display driver paths.
  • If no vendor fix is listed, follow Linux distribution or kernel maintainer guidance.

Validation and detection

  • Inventory Linux kernels and AMD display hardware or driver usage.
  • Map installed kernel packages to vendor advisories or the referenced stable commits.
  • Confirm patched kernels are running after reboot, not merely installed.
  • Review distribution changelogs for CVE-2023-53780 or the referenced commits.
Prepared
Confidence
medium
Sources
5

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-53780 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
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7cunaffected
LinuxLinux4.15, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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