VYPR
Unrated severityNVD Advisory· Published Dec 9, 2025· Updated Apr 15, 2026

CVE-2023-53837

CVE-2023-53837

Description

In the Linux kernel, the following vulnerability has been resolved:

drm/msm: fix NULL-deref on snapshot tear down

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/525099/

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A NULL-pointer dereference in the MSM DRM driver during deinitialization can be triggered when kms is already NULL, leading to a crash.

Vulnerability

Overview

In the Linux kernel's MSM DRM subsystem, a NULL-pointer dereference bug exists in the deinitialization path of the display controller. The issue occurs when the kms pointer is already NULL due to early initialization errors or on platforms that do not use the DPU controller. The deinitialization code does not properly check for this condition before dereferencing the pointer, leading to a potential system crash [1][2].

Exploitation

Context

The vulnerability can be triggered during driver shutdown or error cleanup paths. No special privileges or user interaction are required, as the bug manifests during normal driver lifecycle operations. Attackers with local access or the ability to trigger device removal or driver unbind operations could potentially exploit this to cause a denial-of-service condition [1].

Impact

Successful exploitation leads to a system crash (oops) due to dereferencing a NULL pointer. This can result in a denial of service, making the system unavailable. The vulnerability does not appear to allow privilege escalation or arbitrary code execution based on the available description [1][2].

Mitigation

The fix has been applied in the Linux kernel stable trees, as referenced in the commit that adds a NULL check before the kms pointer is used during tear down. Users are advised to update their kernels to include this patch. No workaround exists other than applying the kernel update [1][2].

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

2

Patches

5

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

5

News mentions

0

No linked articles in our index yet.