LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53534: drm/mediatek: mtk_drm_crtc: Add checks for devm_kcalloc

In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: mtk_drm_crtc: Add checks for devm_kcalloc As the devm_kcalloc may return NULL, the return value needs to be checked to avoid NULL poineter dereference.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the MediaTek display driver. A failed memory allocation could be used without checking for NULL, causing a kernel NULL pointer dereference. The public record does not provide CVSS, attack requirements, or confirmed exploitation, so urgency depends on whether affected MediaTek DRM code exists in your kernels.

Executive priority

Treat as a targeted kernel reliability risk, not an internet-wide emergency based on current evidence. Prioritize validation on MediaTek-based devices, embedded products, and custom kernel fleets, then patch through normal kernel maintenance channels.

Technical view

The fix adds checks around devm_kcalloc in drm/mediatek mtk_drm_crtc to prevent NULL pointer dereference after allocation failure. The source bundle lists Linux kernel versions as affected and provides multiple stable kernel commits. No CWE, CVSS vector, privilege requirement, or trigger path is provided.

Likely exposure

Exposure appears limited to Linux systems with affected kernels containing the MediaTek DRM CRTC code path. The supplied affected-version data is incomplete and should be confirmed against exact kernel source, distribution backports, and device vendor kernels.

Exploitation context

The bundle marks KEV as false and provides no evidence of active exploitation or public weaponization. A NULL pointer dereference in kernel code commonly implies crash or denial-of-service risk, but the sources do not establish reachability, required privileges, or remote exploitability.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability details, or concrete trigger conditions are provided. Analysis should focus on commit diff review, affected branch mapping, downstream backports, and whether allocation failure can be attacker-influenced in realistic display-driver workflows.

Mitigation direction

  • Identify kernels using the MediaTek DRM driver code path.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution and device vendor advisories for backported patches.
  • Track kernel source provenance for embedded or custom builds.
  • Do not assume version numbers alone reflect downstream patch status.

Validation and detection

  • Compare deployed kernel trees against the referenced stable commits.
  • Confirm mtk_drm_crtc includes NULL checks after devm_kcalloc.
  • Inventory devices running affected Linux kernel versions from the bundle.
  • Review vendor changelogs for CVE-2023-53534 or matching commit IDs.
  • Document whether MediaTek DRM is built, loaded, or unused.
Prepared
Confidence
medium
Sources
7

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-53534 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
6Source 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
LinuxLinux31c5558dae0513bd2bae33ea37543f584c6c35a5, 31c5558dae0513bd2bae33ea37543f584c6c35a5, 31c5558dae0513bd2bae33ea37543f584c6c35a5, 31c5558dae0513bd2bae33ea37543f584c6c35a5, 31c5558dae0513bd2bae33ea37543f584c6c35a5unaffected
LinuxLinux5.5, 0, 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.