CVE-2024-36014

What it actually does

Null pointer dereference in malidp_mw_connector_reset when kzalloc allocation succeeds without a subsequent null check before invoking __drm_atomic_helper_connector_reset, enabling memory corruption in the Linux kernel DRM Mali display pipeline.

Why it matters to the business

Kernel-level graphics driver instability can trigger system crashes or denial-of-service conditions on affected Linux systems; low EPSS and absence from KEV indicate limited immediate operational disruption, though unpatched systems remain exposed to potential future exploitation.

How an attack unfolds

An attacker triggers memory pressure or allocation failure during connector reset in the Mali display pipeline, causing the unchecked pointer to be dereferenced and resulting in a kernel crash or controlled memory corruption that could be leveraged for privilege escalation or further attacks.

How to fix it

Update to a fixed kernel version that adds the missing null check for mw_state after kzalloc in malidp_mw_connector_reset; apply the resolution referenced in commit 37142be4dc5831114a375392e86d6450d4951c06 for any downstream packages.

How to confirm the fix worked

Confirm the presence of the null-check patch in malidp_mw_connector_reset and verify that mw_state is validated before __drm_atomic_helper_connector_reset is called; test allocation-failure paths to ensure no dereference occurs.

Typical attack path

1. Identify systems running vulnerable Linux kernel versions with Mali display hardware
2. Induce memory allocation failure during drm connector reset operations
3. Trigger null dereference to crash the kernel or attempt memory corruption exploitation

How to detect it

Inspect kernel logs for null pointer dereference oops messages originating from malidp_mw_connector_reset or drm atomic helper paths; correlate with memory allocation failure events in dmesg or journalctl.

What your security team should do

• Prioritize kernel updates on all systems using Mali display drivers
• Monitor for memory-pressure conditions that could surface the dereference
• Review graphics subsystem logs for unexpected connector reset failures