CVE-2025-21819: Revert "drm/amd/display: Use HW lock mgr for PSR1"
In the Linux kernel, the following vulnerability has been resolved:
Revert "drm/amd/display: Use HW lock mgr for PSR1"
This reverts commit
a2b5a9956269 ("drm/amd/display: Use HW lock mgr for PSR1")
Because it may cause system hang while connect with two edp panel.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can make some AMD display systems hang when connected with two embedded DisplayPort panels. The impact described is availability, not data theft or remote compromise. Business urgency depends on whether affected kernel builds run on laptops, kiosks, workstations, or appliances using that display configuration.
Executive priority
Handle through normal patch management, with higher priority for business-critical Linux endpoints or appliances matching the AMD dual-panel display condition. There is no source-backed evidence of active exploitation, but repeated hangs can create operational disruption.
Technical view
The vulnerability is a Linux DRM/AMD display regression fixed by reverting commit a2b5a9956269, which used the hardware lock manager for PSR1. The stated failure mode is a system hang with two eDP panels. The source bundle provides no CVSS, CWE, exploit detail, or complete affected-range clarity.
Likely exposure
Exposure appears limited to Linux systems using the AMD display driver path and the two-eDP-panel condition described by the kernel fix. Organizations should prioritize hardware fleets where display hangs affect operations, support, or device availability.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The available evidence points to a reliability-triggered system hang rather than a known remotely exploitable attack path. Exploitability details are incomplete.
Researcher notes
Research should focus on affected kernel version mapping and the AMD DRM PSR1 hardware-lock change. The CVE data is sparse: no CVSS, CWE, exploit status, or detailed trigger analysis beyond the two-eDP-panel hang statement.
Mitigation direction
Check vendor kernel advisories for affected and fixed package versions.
Prioritize kernel updates on AMD display systems with dual eDP panels.
Use distribution security updates rather than direct kernel deployment where possible.
Track Debian LTS guidance if using Debian-supported kernels.
Avoid inventing workarounds; follow Linux or distribution guidance.
Validation and detection
Inventory Linux kernel versions across affected hardware fleets.
Identify systems using AMD display components and embedded DisplayPort panels.
Compare installed kernels against vendor or distribution fixed versions.
Review incident reports for unexplained display-related hangs.
Confirm updates include the referenced stable kernel revert commits.
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-2025-21819 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
1ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 20:04 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.