CVE-2026-68248

What it actually does

Missing NULL check on GFP_ATOMIC allocation failure in active_instance allows returning an invalid pointer instead of NULL, enabling potential memory corruption or invalid access in the i915 driver.

Why it matters to the business

Low-urgency risk of graphics-related kernel instability or crashes on systems experiencing memory pressure; minimal operational disruption expected given low exploit likelihood and downward EPSS trend.

How an attack unfolds

An attacker triggers an out-of-memory condition during GFP_ATOMIC allocation inside the i915 active_instance function and then uses the erroneously returned non-NULL pointer to corrupt memory or cause a crash.

How to fix it

Update the Linux kernel to a version containing commit 6029bc064f0b1bac184203a50fbaaf070fa18832 or later that returns NULL on allocation error.

How to confirm the fix worked

Confirm the patched active_instance function explicitly returns NULL after a failed GFP_ATOMIC allocation and that callers handle the NULL case.

Typical attack path

1. Force memory pressure on the target system
2. Invoke code paths exercising the i915 active_instance function
3. Trigger allocation failure and receive invalid pointer
4. Leverage the pointer for memory corruption or denial of service

How to detect it

Review kernel logs and dmesg for i915 driver oops, warnings, or allocation failures around GFP_ATOMIC in active_instance; correlate with any sudden graphics instability.

What your security team should do

• Prioritize kernel updates during normal maintenance cycles given low EPSS and absence from KEV
• Monitor kernel logs for i915-related allocation failures or crashes
• Test graphics workloads under memory-constrained conditions after patching