CVE-2023-54138: drm/msm: fix NULL-deref on irq uninstall
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: fix NULL-deref on irq uninstall
In case of early initialisation errors and on platforms that do not use
the DPU controller, the deinitilisation code can be called with the kms
pointer set to NULL.
Patchwork: https://patchwork.freedesktop.org/patch/525104/
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system component when the Qualcomm/MSM graphics driver cleanup path runs after early initialization failures. The public record describes a NULL pointer dereference, not data theft or remote code execution. Business urgency depends on whether affected kernels and relevant MSM graphics hardware or platforms are in use.
Executive priority
Handle through normal kernel patch management unless your environment relies on Qualcomm/MSM graphics platforms. There is no source-provided evidence of active exploitation or remote compromise, but kernel crash risk can still affect device availability.
Technical view
CVE-2023-54138 is a Linux kernel drm/msm NULL dereference during IRQ uninstall. The deinitialization path may be called with the kms pointer set to NULL, including early initialization failures and platforms not using the DPU controller. Stable kernel commits are referenced as fixes, but CVSS, CWE, and detailed impact are not provided.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the drm/msm driver path present. The source lists Linux kernel 5.15 through 6.4-related affected version data, but does not provide CPEs, distributions, hardware models, or package names.
Exploitation context
The source bundle does not show KEV listing, active exploitation, exploit availability, or attacker prerequisites. The described failure mode is a kernel NULL dereference in driver teardown, so the defensible assumption is potential denial of service until vendor guidance clarifies impact.
Researcher notes
The record is sparse: no CVSS, CWE, exploit status, prerequisites, or distribution mappings are supplied. Treat affected-version data carefully and validate against the exact kernel tree or vendor package because stable backports may change exposure conclusions.
Mitigation direction
Update to a vendor or stable kernel containing the referenced drm/msm fix.
Prioritize systems using Qualcomm/MSM graphics or kernels with drm/msm enabled.
Check Linux distribution advisories for backported fixes and package-specific status.
Avoid assuming unaffected status from upstream version alone; vendors may backport patches.
Validation and detection
Inventory running kernel versions across Linux hosts and devices.
Check whether drm/msm support is built in or loaded as a module.
Confirm the deployed kernel includes one of the referenced stable fixes or a vendor backport.
Review kernel crash logs for drm/msm NULL dereference symptoms during initialization or teardown.
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-54138 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
0ADP providers
6Source 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.
Dec 24, 2025, 13:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.