CVE-2024-49908

What it actually does

Null pointer dereference in amdgpu_dm_update_cursor when 'afb' is used without a prior null check after an assumption it could be null, allowing memory corruption on AMD display paths in the Linux kernel.

Why it matters to the business

Potential kernel crashes or system instability on systems with AMD GPUs, leading to downtime and requiring kernel updates; low exploitation likelihood reduces urgency but patch adoption is still needed across Linux distributions.

How an attack unfolds

An attacker with local access triggers display cursor update operations that reach the vulnerable code path with a crafted or null afb structure; listed threat actors in Linux kernel campaigns could chain this with other memory issues for denial of service or limited code execution, though no public exploits are known.

How to fix it

Update the Linux kernel to include commit a742168b6a39ead257da53bcbe472384d6e14a1b in affected stable trees; apply distribution-specific kernel packages that backport the null check.

How to confirm the fix worked

Verify the presence of the null check for 'afb' immediately before its use in amdgpu_dm.c around line 8433 and confirm the running kernel contains the referenced commit or equivalent fix.

Typical attack path

1. Obtain local access on a vulnerable Linux system with AMD display hardware
2. Trigger amdgpu_dm_update_cursor via display or cursor manipulation APIs
3. Supply input that leaves 'afb' null at the dereference site
4. Cause null pointer dereference leading to kernel panic or corruption

How to detect it

Review kernel logs for oops or panic messages referencing amdgpu_dm_update_cursor and null pointer dereference; correlate with display or cursor activity from processes.

What your security team should do

• Prioritize kernel updates on AMD GPU systems within standard patch cycles
• Monitor kernel logs for null pointer dereference oops in amdgpu_dm_update_cursor
• Restrict unprivileged local access where possible until patched