CVE-2024-42122

What it actually does

Missing NULL pointer validation after kzalloc in the AMD display driver code path allows dereference of a potentially NULL allocation result, leading to memory corruption.

Why it matters to the business

Kernel panics or instability on systems using AMD graphics hardware, resulting in unplanned downtime and potential data loss for users running affected Linux kernels.

How an attack unfolds

An attacker induces memory pressure to force kzalloc failure then triggers the vulnerable AMD display initialization or mode-setting code path to dereference the unchecked pointer, causing a crash; low exploitability is reflected in stable low EPSS with no known threat actor campaigns.

How to fix it

Update the Linux kernel to a version containing commit 552e7938b4d7fe548fbf29b9950a14c6149d0470 or later; rebuild and deploy the fixed kernel across all affected systems.

How to confirm the fix worked

Inspect the drm/amd/display source for the added NULL check immediately after kzalloc and confirm the running kernel includes the referenced commit or a backport.

Typical attack path

1. Create memory pressure to cause allocation failure
2. Trigger drm/amd/display code path that performs kzalloc
3. Dereference the unchecked NULL pointer resulting in kernel fault

How to detect it

Review kernel ring buffer and dmesg logs for oops/panic entries referencing drm/amd/display kzalloc failures or NULL dereferences around the published date.

What your security team should do

• Prioritize kernel upgrades on all AMD GPU systems within standard patch windows
• Test the updated kernel in staging environments before broad deployment
• Monitor kernel logs for display-related oops until patches are applied