CVE-2024-56667

What it actually does

NULL pointer dereference in drm/i915 capture_engine when intel_context structure is NULL, causing crash during drm_info() call.

Why it matters to the business

System instability and denial of service on Linux systems using Intel graphics hardware, potentially disrupting operations until patched.

How an attack unfolds

An attacker with local access triggers graphics operations that leave intel_context NULL, leading capture_engine to dereference it and crash the kernel.

How to fix it

Update to fixed kernel versions containing commit e07f9c92bd127f8835ac669d83b5e7ff59bbb40f or apply equivalent stable patches; for listed Ubuntu packages use the referenced opencv updates where applicable.

How to confirm the fix worked

Verify kernel version includes the referenced commit, reproduce graphics workloads that previously triggered the NULL path, and confirm absence of dereference crashes in drm logs.

Typical attack path

1. Obtain local access to a vulnerable Linux system with Intel i915 graphics
2. Craft or trigger graphics API calls that result in NULL intel_context
3. Invoke capture_engine path causing NULL dereference and kernel panic

How to detect it

Review kernel logs for drm/i915 capture_engine NULL pointer dereference panics or oops entries around the time of graphics activity.

• capture_engine
• intel_context
• drm_info

What your security team should do

• Apply kernel updates immediately on all Intel graphics systems
• Monitor for kernel oops reports involving drm/i915
• Test graphics subsystems post-update before widespread deployment