CVE-2024-49916

What it actually does

Null pointer dereference in dcn401_init_hw when dc->clk_mgr or dc->clk_mgr->funcs is null before function pointer access.

Why it matters to the business

Potential system instability or crash on affected AMD graphics hardware running vulnerable Linux kernels, disrupting user sessions and workloads until patched.

How an attack unfolds

An attacker with local access crafts conditions during display hardware initialization that leave clk_mgr uninitialized, triggering the dereference and resulting in a kernel panic or denial of service; listed threat actors have targeted similar kernel resource issues in broader campaigns.

How to fix it

Apply the fix from commit ac1c41e318074d8a9ea925787e366be15d7645e8 or upgrade to a kernel containing the patch; affected packages such as vinagre on Rocky Linux 8 should be updated to 3.22.0-23.el8 or later.

How to confirm the fix worked

Confirm the presence of the NULL check for clk_mgr and clk_mgr->funcs in dcn401_hwseq.c around line 416; recompile and test initialization paths under conditions that previously assumed non-null values.

Typical attack path

1. Obtain local access on a Linux system with AMD display hardware using the dcn401 code path.
2. Trigger display driver initialization or mode-setting operations that reach dcn401_init_hw with clk_mgr unset.
3. Cause the unchecked access to clk_mgr->funcs, resulting in a null dereference and kernel fault.

How to detect it

Review kernel logs for null pointer dereference oops messages referencing dcn401_init_hw or clk_mgr; correlate with display driver load events in dmesg or journalctl on systems running vulnerable kernels.

What your security team should do

• Prioritize kernel updates on all AMD-based Linux systems within standard patch windows given low EPSS but broad kernel exposure.
• Monitor for related kernel oops reports in system logs after applying changes.
• Review downstream dependents of the stable Linux GIT repository for coordinated updates.