{"id":"CVE-2024-57985","state":"PUBLISHED","title":"firmware: qcom: scm: Cleanup global '__scm' on probe failures","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Cleanup global '__scm' on probe failures\n\nIf SCM driver fails the probe, it should not leave global '__scm'\nvariable assigned, because external users of this driver will assume the\nprobe finished successfully.  For example TZMEM parts ('__scm->mempool')\nare initialized later in the probe, but users of it (__scm_smc_call())\nrely on the '__scm' variable.\n\nThis fixes theoretical NULL pointer exception, triggered via introducing\nprobe deferral in SCM driver with call trace:\n\n  qcom_tzmem_alloc+0x70/0x1ac (P)\n  qcom_tzmem_alloc+0x64/0x1ac (L)\n  qcom_scm_assign_mem+0x78/0x194\n  qcom_rmtfs_mem_probe+0x2d4/0x38c\n  platform_probe+0x68/0xc8","publishedAt":"2025-02-27T02:07:09.983Z","updatedAt":"2026-10-15T21:51:50.141Z","severity":{"score":7,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"390d3baeba51a126f75c97b90ec28b9384ce4b84","versionType":"git"},{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"faf1715798fe72b79e4432ce8c6d03ca69765425","versionType":"git"},{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"1e76b546e6fca7eb568161f408133904ca6bcf4f","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/firmware/qcom/qcom_scm.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.11","versionType":"semver"},{"version":"6.12.13","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.13.2","status":"unaffected","lessThanOrEqual":"6.13.*","versionType":"semver"},{"version":"6.14","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/firmware/qcom/qcom_scm.c"]}],"references":["https://git.kernel.org/stable/c/390d3baeba51a126f75c97b90ec28b9384ce4b84","https://git.kernel.org/stable/c/faf1715798fe72b79e4432ce8c6d03ca69765425","https://git.kernel.org/stable/c/1e76b546e6fca7eb568161f408133904ca6bcf4f"],"weaknesses":[],"ingestedAt":"2026-10-29T20:08:12.933Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2024/57xxx/CVE-2024-57985.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-57985","state":"PUBLISHED","datePublished":"2025-02-27T02:07:09.983Z","dateUpdated":"2026-10-15T21:51:50.141Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2025-02-27T02:04:28.913Z"},"containers":{"cna":{"title":"firmware: qcom: scm: Cleanup global '__scm' on probe failures","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Cleanup global '__scm' on probe failures\n\nIf SCM driver fails the probe, it should not leave global '__scm'\nvariable assigned, because external users of this driver will assume the\nprobe finished successfully.  For example TZMEM parts ('__scm->mempool')\nare initialized later in the probe, but users of it (__scm_smc_call())\nrely on the '__scm' variable.\n\nThis fixes theoretical NULL pointer exception, triggered via introducing\nprobe deferral in SCM driver with call trace:\n\n  qcom_tzmem_alloc+0x70/0x1ac (P)\n  qcom_tzmem_alloc+0x64/0x1ac (L)\n  qcom_scm_assign_mem+0x78/0x194\n  qcom_rmtfs_mem_probe+0x2d4/0x38c\n  platform_probe+0x68/0xc8"}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"390d3baeba51a126f75c97b90ec28b9384ce4b84","versionType":"git"},{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"faf1715798fe72b79e4432ce8c6d03ca69765425","versionType":"git"},{"version":"40289e35ca525f29a03989352ab207b6a9675475","status":"affected","lessThan":"1e76b546e6fca7eb568161f408133904ca6bcf4f","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/firmware/qcom/qcom_scm.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.11","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.11","versionType":"semver"},{"version":"6.12.13","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.13.2","status":"unaffected","lessThanOrEqual":"6.13.*","versionType":"semver"},{"version":"6.14","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/firmware/qcom/qcom_scm.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/390d3baeba51a126f75c97b90ec28b9384ce4b84"},{"url":"https://git.kernel.org/stable/c/faf1715798fe72b79e4432ce8c6d03ca69765425"},{"url":"https://git.kernel.org/stable/c/1e76b546e6fca7eb568161f408133904ca6bcf4f"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The Qualcomm SCM driver is a platform firmware interface (SMC calls to TrustZone) with no network-facing surface; reaching the stale `__scm` requires local access to a consumer entry point such as the msm DRM render node or `/dev/fastrpc-*`.\nAC:H - The vulnerable state only exists if `qcom_scm_probe()` fails or defers after publishing `__scm` — a boot-time device-tree/driver-ordering condition the attacker cannot induce, and `suppress_bind_attrs = true` plus `subsys_initcall` registration removes any bind/unbind or module-reload path to force a re-probe.\nPR:L - Once the dangling `__scm` exists, an ordinary unprivileged local user can reach it — the a6xx zap-shader load path (`adreno_zap_shader_load()` from `a6xx_gpu.c:995`) is driven by GPU init on the msm render node, which unprivileged apps hold on Android, and `fastrpc` exposes another unprivileged device node.\nUI:N - No victim action is required; the stale pointer is consumed automatically by subsequent driver probes at boot or by the attacker's own GPU/fastrpc activity.\nS:U - The freed object, the dereferences, and any resulting corruption are all within the kernel's own security authority, with no crossing into a hypervisor, IOMMU, or other domain.\nC:H - This is a use-after-free of a `devm_kzalloc()`'d `struct qcom_scm` released by `devres_release_all()`; consumers read `mempool`, `dev`, and clk/icc pointers out of the reallocated slab object and use them as pointers, which per UAF scoring can be leveraged into arbitrary kernel memory disclosure.\nI:H - Controlling the reallocated object gives control of `__scm->mempool` (fed to `gen_pool_alloc()`) and `__scm->core_clk`/`__scm->path` (consumed by `clk_enable()`/`icc_set_bw()`, which chase `ops` function pointers), providing heap-spray-based write and control-flow-hijack primitives.\nA:H - The documented outcome is a kernel oops — a NULL/invalid dereference in `qcom_tzmem_alloc()` via `qcom_scm_assign_mem()` — and use-after-frees reliably panic the kernel even when not weaponized."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T11:47:11.635Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.12.13"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.13.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.14"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2024-57985","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"version":"2.0.3","timestamp":"2026-10-15T21:41:53.306384Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-15T21:51:50.141Z"}}]}}}