CVE-2024-56775: drm/amd/display: Fix handling of plane refcount
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix handling of plane refcount
[Why]
The mechanism to backup and restore plane states doesn't maintain
refcount, which can cause issues if the refcount of the plane changes
in between backup and restore operations, such as memory leaks if the
refcount was supposed to go down, or double frees / invalid memory
accesses if the refcount was supposed to go up.
[How]
Cache and re-apply current refcount when restoring plane states.
Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver bookkeeping flaw can mishandle graphics-plane references during state restoration. Under the stated local, low-privilege attack model, it may cause memory corruption, crashes, or potentially compromise the affected system. The source bundle rates it CVSS 7.8.
Executive priority
Treat as a high-priority endpoint remediation issue, especially on shared AMD-graphics systems. It is not evidenced as remotely or actively exploited, so prioritize below confirmed-exploited critical vulnerabilities while patching promptly through normal kernel maintenance.
Technical view
The AMD DRM display code backed up and restored plane state without preserving its current reference count. If that count changed between operations, restoration could produce leaks, double frees, or invalid memory access. The kernel fix caches the current count and reapplies it during restoration.
Likely exposure
Exposure requires an affected Linux kernel using the AMD display subsystem. The supplied version data identifies 4.15, 6.12.4, and 6.13 but does not provide sufficiently clear range semantics; verify distribution backports and kernel provenance individually.
Exploitation context
The CVSS vector describes local exploitation requiring low privileges, low complexity, and no user interaction, with possible confidentiality, integrity, and availability impact. The bundle marks KEV false and supplies no evidence of active exploitation or a public exploit.
Researcher notes
The record maps CWE-415 and describes double-free, invalid-access, and leak outcomes caused by stale plane reference counts. Exact reachability, triggering conditions, affected range boundaries, and exploitability beyond the CVSS assumptions are not established by the supplied evidence.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced plane-refcount fix.
Check distribution security guidance for backported fixes rather than relying only on upstream version numbers.
Prioritize multi-user workstations and other systems where untrusted local users can access affected graphics functionality.
If immediate updating is impossible, restrict untrusted local access and follow vendor-provided mitigations.
Validation and detection
Inventory Linux kernel versions and identify systems using AMD display hardware or drivers.
Confirm the installed kernel includes either referenced fix or an equivalent vendor backport.
Review vendor advisories and package changelogs because distribution kernel versions may not match upstream numbering.
After updating, verify the fixed kernel is running and affected older kernels are no longer booted.
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.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.