CVE-2024-42310

What it actually does

Null pointer dereference in the cdv_intel_lvds_get_modes function of the gma500 DRM driver when drm_mode_duplicate fails to allocate a mode structure.

Why it matters to the business

Local denial of service on Linux systems using Intel GMA500 graphics hardware, with potential for system instability affecting 15 downstream dependents; urgency is moderate given low EPSS and absence from known exploited lists.

How an attack unfolds

An attacker with local access invokes the LVDS mode retrieval path in the kernel DRM subsystem, causing drm_mode_duplicate to return NULL and triggering an immediate kernel crash via subsequent pointer dereference.

How to fix it

Apply kernel patches updating org/pub/scm/linux/kernel/git/stable/linux.git to commit f392c36cebf4c1d6997a4cc2c0f205254acef42a; for decode-uri-component update to 0.2.1 if present in the environment.

How to confirm the fix worked

Verify the presence of the NULL check after drm_mode_duplicate in cdv_intel_lvds_get_modes in the running kernel source or confirm the fixed commit hash is included in the deployed kernel.

Typical attack path

1. Obtain local user access on an affected Linux kernel
2. Trigger DRM LVDS mode enumeration through graphics initialization or display hotplug
3. Force drm_mode_duplicate failure to induce NULL assignment
4. Trigger dereference leading to kernel panic or oops

How to detect it

Inspect kernel logs and crash dumps for null pointer dereference oops containing cdv_intel_lvds_get_modes or gma500 driver references; correlate with local user sessions on affected hardware.

• cdv_intel_lvds_get_modes
• gma500
• drm_mode_duplicate

What your security team should do

• Prioritize patching affected Linux kernel packages to the listed fixed commit within standard maintenance windows
• Monitor for kernel oops reports referencing gma500 or cdv_intel_lvds_get_modes
• Limit local user access on systems with GMA500 hardware until patched