LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54122: drm/msm/dpu: Add check for cstate

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Add check for cstate As kzalloc may fail and return NULL pointer, it should be better to check cstate in order to avoid the NULL pointer dereference in __drm_atomic_helper_crtc_reset. Patchwork: https://patchwork.freedesktop.org/patch/514163/

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54122 is a Linux kernel display-driver bug. If memory allocation fails, the driver could pass a null state object into reset logic and crash the kernel path. The public record does not provide CVSS, CWE, impact scope, or exploitation evidence.

Executive priority

Handle through normal kernel patch management unless impacted devices are business-critical or crash-sensitive. The urgency is constrained by missing severity scoring and no active exploitation evidence in the provided sources.

Technical view

The issue is in drm/msm/dpu. A kzalloc failure could leave cstate NULL, leading to a NULL pointer dereference in __drm_atomic_helper_crtc_reset. The upstream resolution adds a cstate check, with multiple stable kernel commit references listed for backports.

Likely exposure

Exposure appears limited to Linux systems using the Qualcomm MSM/DPU DRM display stack and affected kernel versions. Distribution kernels may differ because of vendor backports, so source package and running-kernel verification are required.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit use, or remote attack path. Treat this as an availability-risk kernel bug unless vendor guidance says otherwise.

Researcher notes

The public evidence identifies root cause and fix direction but not reachability, privilege requirements, or full affected-version ranges. Validate against exact kernel trees, configs, and downstream patches before assigning operational severity.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Confirm distribution vendor kernels include the cstate NULL-check backport.
  • Prioritize affected Qualcomm MSM/DPU systems where display stability is operationally important.
  • Track vendor advisories because the source bundle lacks CVSS and detailed impact guidance.

Validation and detection

  • Inventory Linux hosts and embedded devices using drm/msm/dpu.
  • Check running kernel versions against vendor-fixed packages or referenced stable commits.
  • Review kernel source or changelog for the cstate NULL-check fix.
  • Monitor kernel logs for display reset crashes or NULL pointer dereference traces.
Prepared
Confidence
medium
Sources
8

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-54122 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
7Source 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
LinuxLinux1cff7440a86e04a613665803b42034c467f035fa, 1cff7440a86e04a613665803b42034c467f035fa, 1cff7440a86e04a613665803b42034c467f035fa, 1cff7440a86e04a613665803b42034c467f035fa, 1cff7440a86e04a613665803b42034c467f035fa, 1cff7440a86e04a613665803b42034c467f035faunaffected
LinuxLinux5.3, 0, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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