LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53864: drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash the kernel when a specific display overlay plane is disabled in the mxsfb DRM driver. The issue is a NULL pointer dereference, so the business concern is system availability rather than confirmed data theft or remote compromise.

Executive priority

Handle through normal kernel patch management, with higher urgency for embedded or appliance systems depending on mxsfb display hardware. There is no source-backed evidence of active exploitation or remote compromise.

Technical view

The mxsfb DRM overlay disable path could dereference a NULL framebuffer pointer when overlay handling occurred in mxsfb_plane_overlay_atomic_update(). The fix moves overlay plane disabling into mxsfb_plane_overlay_atomic_disable(), avoiding the NULL framebuffer dereference and resulting kernel Oops.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the mxsfb DRM driver and overlay plane functionality in use. The source bundle does not establish broad default exposure across all Linux deployments.

Exploitation context

No KEV listing or cited source reports active exploitation. The bundle does not describe remote reachability, required privileges, or public exploit code. Treat this as a potential local or device-specific availability issue unless vendor guidance says otherwise.

Researcher notes

The available evidence identifies the faulty code path and stable fixes, but omits CVSS, CWE, exploitability prerequisites, and distribution-specific package status. Validation should focus on driver presence, kernel lineage, and whether vendor kernels backport the fix.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize systems using the mxsfb DRM display driver.
  • Check Linux distribution advisories for backported fixes.
  • If patching is delayed, monitor for mxsfb-related kernel Oops events.

Validation and detection

  • Inventory kernel versions against affected and fixed ranges.
  • Confirm whether the mxsfb DRM driver is present or loaded.
  • Review kernel logs for NULL pointer dereference Oops events.
  • Verify deployed kernels include one of the referenced stable commits.
Prepared
Confidence
medium
Sources
5

Public sources used

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-53864 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcb285a5348e768dbc8edfe28cc2be5ec0c7e1a33, cb285a5348e768dbc8edfe28cc2be5ec0c7e1a33, cb285a5348e768dbc8edfe28cc2be5ec0c7e1a33unaffected
LinuxLinux5.19, 0, 6.1.54, 6.5.4, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.