CVE-2024-43909

What it actually does

Null pointer dereference in the AMD GPU power management code path for smu7 hardware managers when hwmgr->backend is passed as NULL to smu7_update_edc_leakage_table.

Why it matters to the business

Potential system instability or crash on affected Linux systems using AMD GPUs, increasing downtime risk for workloads relying on those graphics cards; low exploitation likelihood reduces urgency but kernel-level impact requires prompt patching across fleets.

How an attack unfolds

An attacker with local access triggers the vulnerable power management function on an AMD smu7 GPU by causing the backend pointer to be NULL, leading to dereference during leakage table updates; no widespread exploitation reported despite mentions of general Linux kernel campaigns.

How to fix it

Update the Linux kernel to the fixed commit 37b9df457cbcf095963d18f17d6cb7dfa0a03fce in the stable repository or apply equivalent backported patches; rebuild and deploy the updated kernel image across all affected systems.

How to confirm the fix worked

Verify the running kernel source contains commit 37b9df457cbcf095963d18f17d6cb7dfa0a03fce; test GPU power management functions with null backend inputs to confirm absence of dereference.

Typical attack path

1. Obtain local code execution on a Linux system with AMD smu7 GPU
2. Trigger GPU power management operations that invoke smu7_update_edc_leakage_table with null backend
3. Cause null pointer dereference resulting in kernel panic or crash

How to detect it

Review kernel logs for null pointer dereference crashes in amdgpu or smu7 power management paths; no confirmed in-the-wild exploitation indicators available.

What your security team should do

• Prioritize kernel updates on systems with AMD GPUs within standard maintenance windows
• Monitor for new Linux kernel releases containing the referenced commit
• Review internal GPU driver usage for smu7 hardware to assess exposure breadth