CVE-2024-49921

What it actually does

Missing null pointer validation on previously-checked pointers such as dc->clk_mgr inside AMD display driver code paths creates potential for dereference of a null value, triggering kernel faults.

Why it matters to the business

Linux systems with AMD GPUs may experience unexpected crashes or display instability; low EPSS and absence from KEV indicate limited immediate operational disruption for most organizations, though kernel updates remain necessary for stability.

How an attack unfolds

An attacker would need local or privileged access to reach the affected display code paths with a null clk_mgr or similar pointer; no public exploitation or named threat actor campaigns are associated with this specific null-check omission.

How to fix it

Apply the upstream fix in commit 5b35bf1a82eb29841b67ff5643ba83762250fc24 or upgrade qt5-qtwebsockets on Rocky Linux 8 to 5.12.5-2.el8; rebuild and reboot with the patched kernel.

How to confirm the fix worked

Verify the presence of commit 5b35bf1a82eb29841b67ff5643ba83762250fc24 in the running kernel source or confirm package version 5.12.5-2.el8; re-run static analysis tools to ensure FORWARD_NULL warnings are resolved.

Typical attack path

1. Obtain local access on a vulnerable Linux kernel with AMD display support
2. Trigger display initialization or clock management code paths that bypass earlier null checks
3. Cause kernel panic or fault via null dereference

How to detect it

Review kernel logs (dmesg, /var/log/kern.log) for null pointer dereference oops associated with amd/display clock management; correlate with display driver initialization events.

What your security team should do

• Prioritize kernel updates on AMD GPU systems within standard patch windows given low EPSS
• Monitor dmesg for AMD display-related faults during routine operations
• Include the fixed commit hash in kernel build and deployment validation pipelines