CVE-2024-56538: drm: zynqmp_kms: Unplug DRM device before removal
In the Linux kernel, the following vulnerability has been resolved:
drm: zynqmp_kms: Unplug DRM device before removal
Prevent userspace accesses to the DRM device from causing
use-after-frees by unplugging the device before we remove it. This
causes any further userspace accesses to result in an error without
further calls into this driver's internals.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux ZynqMP display driver can leave userspace interacting with a device while it is being removed, causing access to freed memory. A low-privileged local user may threaten system confidentiality, integrity, or availability. Exposure is limited to systems using the affected driver and requires local access.
Executive priority
Treat as a high-priority platform patch for exposed ZynqMP systems, particularly shared or locally accessible appliances. It is less urgent for systems without this driver or without untrusted local access. Require asset-specific confirmation because the supplied affected-version data is insufficient for reliable fleet-wide matching.
Technical view
CVE-2024-56538 is a CWE-416 use-after-free in drm/zynqmp_kms. The corrected removal sequence first unplugs the DRM device, making subsequent userspace accesses return errors instead of entering removed driver internals. CVSS 3.1 rates it 7.8: local, low-complexity, low-privilege, no user interaction, with high confidentiality, integrity, and availability impacts.
Likely exposure
Most relevant to Linux systems using the ZynqMP KMS DRM driver where low-privileged users can access the device. The supplied version information is ambiguous and lacks CPEs, so kernel package or distribution exposure cannot be determined from version numbers alone.
Exploitation context
The supplied record indicates a local attack requiring low privileges, not remote exploitation. It is not listed in the supplied KEV data, and the sources provide no evidence of active exploitation or a public working exploit.
Researcher notes
The record repeats commit d76271d22694 and includes an unexplained version “0,” while providing no CPEs. Four stable-tree correction commits are referenced, likely reflecting different maintained branches. Exact introduction and fixed-version boundaries should be established through distribution advisories or commit ancestry; the supplied bundle alone does not support a precise range.
Mitigation direction
Apply a distribution or vendor kernel incorporating the applicable upstream stable correction.
Consult the Linux or device vendor for exact fixed package versions before deployment.
Prioritize systems exposing the ZynqMP DRM device to untrusted local users.
Validation and detection
Identify systems containing or loading the ZynqMP KMS DRM driver.
Record each active kernel package and build, then compare it with vendor guidance.
Confirm the installed kernel includes the applicable stable correction commit.
Regression-test graphics operation and device removal after updating.
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-416: 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
5Source 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.