CVE-2023-54138
Description
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/
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A NULL pointer dereference in the MSM DRM driver's IRQ uninstall path can cause a system crash during early initialization or on non-DPU platforms.
Vulnerability
Details
The Linux kernel's MSM (MSM DRM) driver contains a NULL pointer dereference vulnerability in the IRQ uninstall path. When the driver's initialization fails early or when the system does not use the DPU (Display Processing Unit) controller, the deinitialization code may be invoked with the kms pointer set to NULL. This leads to a NULL pointer dereference when the IRQ uninstall routine attempts to access members of the kms structure.
Exploitation
An attacker would need to trigger the vulnerable code path, which occurs during driver initialization or deinitialization. This can happen on systems with the MSM DRM driver loaded but where early initialization errors occur, or on platforms that lack the DPU controller. The vulnerability is triggered without any special privileges, as it occurs in kernel context during normal driver lifecycle operations. No user interaction is required beyond booting the system or loading the driver.
Impact
A successful NULL pointer dereference results in a kernel crash (oops), leading to a denial of service (DoS). The system may become unstable or reboot. There is no evidence of privilege escalation or data corruption beyond the crash itself.
Mitigation
The vulnerability has been fixed in the Linux kernel stable tree. The fix is included in commits [1][2][3] which are backported to various stable kernel versions. Users should update their kernel to a version containing the fix. No workaround is available other than avoiding the vulnerable code path, which is not practical.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
5e2d1cc82ad50dd8ce825b165bafa985acff972092e34742ecd459c005de3Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
5- git.kernel.org/stable/c/72092e34742e8b34accdadfa7bd9a13cf255a531nvd
- git.kernel.org/stable/c/bafa985acff9b0ed53957beff33c18be08d6b9a6nvd
- git.kernel.org/stable/c/cd459c005de3e2b855a8cc7768e633ce9d018e9fnvd
- git.kernel.org/stable/c/dd8ce825b165acf997689c5ffa45d6a7a1fc0260nvd
- git.kernel.org/stable/c/e2d1cc82ad509c07a9ab0ab4bf88b6613fbf784bnvd
News mentions
0No linked articles in our index yet.