CVE-2024-39466

What it actually does

Missing SCM availability check in the qcom/lmh thermal driver allows null pointer dereference during probe on systems without SCM support.

Why it matters to the business

Linux-based devices using Qualcomm thermal management may crash or become unstable at boot or driver load, disrupting operations and requiring restarts; low EPSS indicates limited observed exploitation risk but kernel-level impact affects many systems.

How an attack unfolds

An attacker triggers driver initialization on a vulnerable kernel without available SCM, causing the un-checked null dereference to occur and potentially leading to a crash; threat actor references to Android kernel RCE suggest possible chaining in mobile or embedded contexts.

How to fix it

Apply the upstream fix adding the SCM availability check at probe time; for affected packages update to the version containing commit c710ff6c753ae9d726c4c2bbdd8440fed834c6a7.

How to confirm the fix worked

Confirm driver probe succeeds without dereference on hardware lacking SCM; verify kernel logs show no null pointer faults from the lmh driver after applying the update.

Typical attack path

1. Identify systems running vulnerable Linux kernel versions with qcom lmh driver enabled
2. Trigger device probe or boot sequence without SCM availability
3. Induce null pointer dereference resulting in kernel panic or denial of service

How to detect it

Review kernel logs and dmesg for null pointer dereference traces involving thermal/drivers/qcom/lmh; check for unexpected panics during boot on affected hardware.

What your security team should do

• Prioritize patching Linux kernels using qcom thermal drivers within standard maintenance windows given low EPSS and no KEV listing
• Monitor for kernel oops or panic events tied to thermal drivers
• Test the fix in representative Qualcomm-based environments before broad deployment