LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57985: firmware: qcom: scm: Cleanup global '__scm' on probe failures

In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Cleanup global '__scm' on probe failures If SCM driver fails the probe, it should not leave global '__scm' variable assigned, because external users of this driver will assume the probe finished successfully. For example TZMEM parts ('__scm->mempool') are initialized later in the probe, but users of it (__scm_smc_call()) rely on the '__scm' variable. This fixes theoretical NULL pointer exception, triggered via introducing probe deferral in SCM driver with call trace: qcom_tzmem_alloc+0x70/0x1ac (P) qcom_tzmem_alloc+0x64/0x1ac (L) qcom_scm_assign_mem+0x78/0x194 qcom_rmtfs_mem_probe+0x2d4/0x38c platform_probe+0x68/0xc8

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Qualcomm SCM driver initialization. If driver probing fails, a global state pointer can remain set, making other kernel code believe initialization succeeded. The source describes a theoretical NULL pointer exception rather than a proven remote compromise.

Executive priority

Treat this as a maintenance-priority kernel reliability issue unless Qualcomm-based systems are business critical. No source evidence supports emergency exploitation response, but affected embedded fleets should receive normal security update handling.

Technical view

The fix clears the global __scm pointer on qcom_scm probe failure. Without cleanup, later users such as __scm_smc_call() may dereference partially initialized SCM/TZMEM state, including __scm->mempool, causing a NULL pointer exception during related Qualcomm memory operations.

Likely exposure

Exposure appears limited to Linux systems using the Qualcomm SCM firmware driver path. The bundle lists Linux as affected, including versions 6.11, 6.12.13, 6.13.2, and 6.14, with incomplete version-range detail.

Exploitation context

The provided sources do not report active exploitation, public exploit availability, or KEV listing. The kernel description frames this as a theoretical crash condition triggered by probe deferral or failure during SCM driver initialization.

Researcher notes

The evidence supports a NULL pointer exception risk from stale global driver state after failed probe. No CVSS, CWE, exploitability assessment, or attacker prerequisites are provided, so impact and reach remain uncertain.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check distribution or device vendor advisories for exact fixed builds.
  • Prioritize Qualcomm SCM-enabled kernels and embedded device fleets.
  • Backport the referenced cleanup patch if maintaining a custom kernel.

Validation and detection

  • Inventory kernels using the Qualcomm SCM driver.
  • Compare deployed kernel source against the referenced stable commits.
  • Review boot logs for SCM probe failures or deferrals.
  • Confirm vendor kernels include the __scm cleanup on probe failure.
Prepared
Confidence
medium
Sources
5

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-57985 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
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40289e35ca525f29a03989352ab207b6a9675475, 40289e35ca525f29a03989352ab207b6a9675475, 40289e35ca525f29a03989352ab207b6a9675475unaffected
LinuxLinux6.11, 0, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

No CWE listed

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