Answer in brief
CVE-2024-57985 records a Unknown severity vulnerability in firmware: qcom: scm: Cleanup global '__scm' on probe failures. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=40289e35ca525f29a03989352ab207b6a9675475 <390d3baeba51a126f75c97b90ec28b9384ce4b84 || >=40289e35ca525f29a03989352ab207b6a9675475 <faf1715798fe72b79e4432ce8c6d03ca69765425 || >=40289e35ca525f29a03989352ab207b6a9675475 <1e76b546e6fca7eb568161f408133904ca6bcf4f | 390d3baeba51a126f75c97b90ec28b9384ce4b84, faf1715798fe72b79e4432ce8c6d03ca69765425, 1e76b546e6fca7eb568161f408133904ca6bcf4f |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-57985 records a Unknown severity vulnerability in firmware: qcom: scm: Cleanup global '__scm' on probe failures. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=40289e35ca525f29a03989352ab207b6a9675475 <390d3baeba51a126f75c97b90ec28b9384ce4b84 || >=40289e35ca525f29a03989352ab207b6a9675475 <faf1715798fe72b79e4432ce8c6d03ca69765425 || >=40289e35ca525f29a03989352ab207b6a9675475 <1e76b546e6fca7eb568161f408133904ca6bcf4f | 390d3baeba51a126f75c97b90ec28b9384ce4b84, faf1715798fe72b79e4432ce8c6d03ca69765425, 1e76b546e6fca7eb568161f408133904ca6bcf4f |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.