CVE-2024-41093

What it actually does

Missing null check on framebuffer object in amdgpu drm code allows dereference of a null pointer via state->fb->obj[0] instead of using drm_gem_fb_get_obj(), resulting in a kernel crash.

Why it matters to the business

Systems using AMD GPUs on affected Linux kernels may experience unexpected crashes or loss of graphics functionality, reducing system availability for users and workloads.

How an attack unfolds

An attacker with local access crafts or triggers a graphics operation that reaches the vulnerable framebuffer handling path in the amdgpu driver, passing a state where the object reference is null and causing a kernel panic.

How to fix it

Update the Linux kernel to the fixed commit 7f35e01cb0ea4d295f5c067bb5c67dfcddaf05bc or later stable releases containing the patch that replaces the direct access with drm_gem_fb_get_obj() and returns an error on null.

How to confirm the fix worked

Confirm the running kernel contains commit 7f35e01cb0ea4d295f5c067bb5c67dfcddaf05bc, review the drm_gem_fb_get_obj call site in amdgpu code, and test graphics initialization and state transitions under load to verify no null dereference occurs.

Typical attack path

1. Obtain local user access on a system with an AMD GPU
2. Trigger a display or rendering operation that exercises the drm amdgpu framebuffer state code
3. Supply or cause a framebuffer state lacking a valid GEM object
4. Trigger the direct obj[0] access resulting in null dereference and crash

How to detect it

Inspect kernel logs for amdgpu-related null pointer dereference oops or panic entries around the time of crashes; examine call stacks referencing drm_gem_fb_get_obj or framebuffer object handling.

What your security team should do

• Apply the kernel update containing commit 7f35e01cb0ea4d295f5c067bb5c67dfcddaf05bc as soon as possible on all AMD GPU systems
• Prioritize patching production and multi-user systems first due to local privilege requirement
• Monitor for kernel oops or panic logs related to amdgpu framebuffer handling
• Review graphics driver usage in container or virtualized environments for exposure