CVE-2024-46835

What it actually does

Potential null pointer dereference when adev->gfx.imu.funcs is NULL in the AMD GPU driver, allowing uninitialized resource use that can lead to memory corruption.

Why it matters to the business

May cause system crashes or instability on Linux systems using AMD GPUs, interrupting workloads; widespread kernel usage increases exposure across servers and desktops despite low exploit likelihood.

How an attack unfolds

An attacker triggers AMD GPU initialization paths in the drm/amdgpu driver where the IMU funcs pointer remains unchecked and NULL; similar Linux kernel resource issues have been targeted in 2024 zero-day campaigns by espionage and financially motivated actors as well as out-of-bounds write attempts.

How to fix it

Update the Linux kernel to commit d40c2c3dd0395fe7fdc19bd96551e87251426d66 or equivalent fixed versions; also apply golang.org/x/crypto update to 0.0.0-20220314234659-1baeb1ce4c0b where applicable.

How to confirm the fix worked

Verify the presence of commit d40c2c3dd0395fe7fdc19bd96551e87251426d66 in the kernel source or confirm updated package versions are deployed across affected systems.

Typical attack path

1. Gain local access to a vulnerable Linux system with AMD GPU hardware
2. Trigger drm/amdgpu driver initialization or specific GPU operations that reach the unchecked pointer
3. Cause NULL dereference resulting in kernel panic or corruption

How to detect it

Search kernel logs for amdgpu-related oops or panics involving IMU or gfx initialization; review for patterns matching Linux kernel use-of-uninitialized-resource or out-of-bounds write attempts noted in 2024 campaigns.

What your security team should do

• Prioritize kernel updates on all AMD GPU Linux systems given the published fix and threat actor interest in similar issues
• Monitor EPSS and KEV status for any change in exploit maturity
• Test updates in staging environments before broad rollout due to high ecosystem prevalence of the kernel