CVE-2024-56537

What it actually does

Null pointer dereference during layer release in zynqmp_disp driver when layer->info is null after an error on the first layer in zynqmp_disp_create_layers, resulting in memory corruption.

Why it matters to the business

Kernel crashes or panics on affected Linux systems disrupt operations and availability; widespread Linux kernel usage and listed threat actor interest elevate organizational risk and remediation urgency.

How an attack unfolds

An attacker with local access triggers an error condition during initial layer creation in the DRM zynqmp_disp path, then forces the release routine to dereference the null layer->info pointer; named actors in 2024 zero-day campaigns and Linux kernel out-of-bounds/memory issues have targeted similar kernel flaws.

How to fix it

Update to fixed kernel commit ce7e62bbd55d20cf250396eb4e8f65b3b5a5e685 or later; for imagemagick on Ubuntu 14.04 LTS upgrade to 8:6.7.7.10-6ubuntu3.2 and on Ubuntu 16.04 LTS to 8:6.8.9.9-7ubuntu5.2.

How to confirm the fix worked

Verify installed kernel or package versions match or exceed the listed fixed revisions; reproduce layer creation error paths in test environments and confirm no null dereference occurs on release.

Typical attack path

1. Gain local access or execute code on target Linux system
2. Trigger error path in zynqmp_disp_create_layers for the first layer
3. Invoke layer release routine that assumes non-null info
4. Cause null dereference leading to crash or corruption

How to detect it

Search kernel logs for zynqmp_disp related null pointer dereference or oops messages; review system crash dumps and dmesg output for layer release failures in DRM subsystem.

• zynqmp_disp_create_layers
• layer->info
• null pointer dereference.*zynqmp

What your security team should do

• Immediately apply the listed fixed kernel commit or package versions due to kernel memory corruption class
• Monitor for kernel oops/panic logs related to zynqmp_disp
• Prioritize systems with ZynqMP DRM hardware exposure