LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability issue in the Qualcomm LMH thermal driver. On some Qualcomm-based systems, the driver may probe before secure-channel support is available, causing a null pointer dereference. The public record does not provide CVSS, broad impact detail, or evidence of active exploitation.

Executive priority

Treat as targeted operational risk, not a broad emergency based on current evidence. Patch through normal kernel maintenance, but accelerate for affected Qualcomm devices showing crashes, boot issues, or thermal-driver instability.

Technical view

The issue is in thermal/drivers/qcom/lmh. Missing SCM availability validation at probe can dereference a null pointer; the kernel fix adds the required availability check. The report cites RB1 as a system where this occurred. Stable kernel commits are referenced, but exploitability and security impact are not detailed.

Likely exposure

Exposure appears limited to Linux systems using the Qualcomm LMH thermal driver on affected kernel lines. Fleets without Qualcomm LMH hardware or driver enablement are likely not exposed. Confirm using kernel version, configuration, and vendor kernel advisories.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The described failure is a null pointer dereference observed during driver probe, which suggests reliability or availability impact, but public evidence is incomplete.

Researcher notes

The CVE record lacks CVSS, CWE, and detailed attack prerequisites. Analysis should stay tied to the driver-probe null dereference and stable commit references. Do not assume remote exploitability, privilege escalation, or affected device models beyond Linux Qualcomm LMH contexts.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Check Linux distribution or device vendor advisories for backported patches.
  • Prioritize Qualcomm-based devices using the qcom LMH thermal driver.
  • Monitor affected systems for probe-time kernel faults or boot instability.

Validation and detection

  • Inventory Linux kernel versions across Qualcomm-based systems.
  • Confirm whether the qcom LMH thermal driver is built or loaded.
  • Compare deployed kernels against vendor-patched releases or referenced stable commits.
  • Review kernel logs for LMH or SCM probe failures.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-39466 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux53bca371cdf7addc1e93e1b99285b3d3935685ec, 53bca371cdf7addc1e93e1b99285b3d3935685ec, 53bca371cdf7addc1e93e1b99285b3d3935685ec, 53bca371cdf7addc1e93e1b99285b3d3935685ec, 53bca371cdf7addc1e93e1b99285b3d3935685ecunaffected
LinuxLinux5.15, 0, 5.15.161, 6.1.94, 6.6.34, 6.9.5, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.