LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36014: drm/arm/malidp: fix a possible null pointer dereference

In the Linux kernel, the following vulnerability has been resolved: drm/arm/malidp: fix a possible null pointer dereference In malidp_mw_connector_reset, new memory is allocated with kzalloc, but no check is performed. In order to prevent null pointer dereferencing, ensure that mw_state is checked before calling __drm_atomic_helper_connector_reset.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-36014 is a Linux kernel flaw in the ARM Mali-DP display driver. If a memory allocation fails, the driver could dereference a null pointer and crash kernel execution. The public sources do not provide CVSS, active exploitation, or remote attack evidence.

Executive priority

Treat this as routine kernel hygiene unless your environment runs ARM Mali-DP display hardware at scale. There is no cited active exploitation, but kernel null dereference bugs can affect availability and should be handled through normal kernel patch cycles.

Technical view

The issue is in drm/arm/malidp, specifically malidp_mw_connector_reset. The code allocated mw_state with kzalloc but did not verify success before passing it into __drm_atomic_helper_connector_reset. Stable kernel commits add the missing null check. Impact appears consistent with denial of service, but source evidence is limited.

Likely exposure

Exposure is most relevant to Linux systems that include and use the ARM Mali-DP DRM driver, commonly ARM-based devices or kernels built with that driver. Generic Linux servers without this driver or hardware are less likely exposed, but kernel configuration and deployed version must be checked.

Exploitation context

The source bundle does not identify public exploitation, weaponized proof of concept, or CISA KEV listing. The described failure path depends on memory allocation failure in a kernel display driver reset path, so practical exploitability is unclear from the available evidence.

Researcher notes

The CVE record lacks CVSS, CWE, and detailed affected range semantics. Analysis should focus on confirming reachable malidp code paths, exact kernel branch status, and whether downstream vendors backported the null-check fix without changing version numbers.

Mitigation direction

  • Update affected Linux kernels to vendor-supported releases containing the stable fixes.
  • Check Debian LTS or distribution advisories for packaged kernel updates.
  • Prioritize systems with ARM Mali-DP hardware or enabled malidp DRM support.
  • If no vendor package is available, track upstream stable commits and vendor guidance.

Validation and detection

  • Inventory kernel versions across ARM and embedded Linux assets.
  • Check whether CONFIG_DRM_MALI_DISPLAY or equivalent malidp support is enabled.
  • Confirm deployed kernel includes one of the referenced stable fixes.
  • Review distribution security advisories for backported kernel patches.
Prepared
Confidence
medium
Sources
12

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-2024-36014 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
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bf, 8cbc5caf36ef7a299b5cbedf55f27fd898d700bfunaffected
LinuxLinux4.19, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

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