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

CVE-2023-53864

CVE-2023-53864

Description

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

drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable()

When disabling overlay plane in mxsfb_plane_overlay_atomic_update(), overlay plane's framebuffer pointer is NULL. So, dereferencing it would cause a kernel Oops(NULL pointer dereferencing). Fix the issue by disabling overlay plane in mxsfb_plane_overlay_atomic_disable() instead.

AI Insight

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

A NULL pointer dereference in the Linux kernel's mxsfb DRM driver could cause a kernel Oops when disabling an overlay plane.

Vulnerability

CVE-2023-53864 is a NULL pointer dereference vulnerability in the Linux kernel's mxsfb DRM driver for i.MX SoCs. The bug occurs in the overlay plane disable path: when mxsfb_plane_overlay_atomic_update() disables the overlay plane, it still tries to dereference the plane's framebuffer pointer, which is NULL at that point. The root cause is that the disable logic was placed in the wrong function—it should have been handled in mxsfb_plane_overlay_atomic_disable(), where the framebuffer pointer is not accessed [1][2][3].

Exploitation

An attacker would need to be able to trigger an atomic display update that disables the overlay plane on a system using the mxsfb driver. This could be achieved through a crafted DRM application (e.g., a Wayland compositor or direct DRM client) that issues a disable operation. No special privileges beyond local user access to /dev/dri/card* are required—a standard unprivileged user can open the DRM device and submit atomic commits. The attack surface is local, as the DRM subsystem is only accessible from userspace on the same machine [1][2][3].

Impact

Successful exploitation causes a kernel NULL pointer dereference, leading to a kernel Oops (panic/BSOD) and denial of service (DoS). Since the bug is in a DRM driver, the system display will freeze or crash, potentially requiring a reboot. No privilege escalation is possible because the crash occurs in kernel context without controlled data leakage [1][2][3].

Mitigation

The fix was committed to the Linux kernel stable trees as commits 0f98de0a11d2, 8bf2d4ca521d, and aa656d48e871, which move the overlay disable code into mxsfb_plane_overlay_atomic_disable(). Users should update to a kernel version containing these commits. No workaround exists besides avoiding the use of overlay planes on affected systems [1][2][3].

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
  • Linux/Kernelinferred2 versions
    (expand)+ 1 more
    • (no CPE)
    • (no CPE)

Patches

3

Vulnerability mechanics

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

References

3

News mentions

0

No linked articles in our index yet.