CVE-2024-57985 (GCVE-0-2024-57985)
Vulnerability from cvelistv5
Published
2025-02-27 02:07
Modified
2026-10-15 21:51
Severity ?
7.0 (High) - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
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
References
Impacted products
Vendor Product Version
Linux Linux Version: 40289e35ca525f29a03989352ab207b6a9675475
Version: 40289e35ca525f29a03989352ab207b6a9675475
Version: 40289e35ca525f29a03989352ab207b6a9675475
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-57985",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-15T21:41:53.306384Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-15T21:51:50.141Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/qcom/qcom_scm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "390d3baeba51a126f75c97b90ec28b9384ce4b84",
              "status": "affected",
              "version": "40289e35ca525f29a03989352ab207b6a9675475",
              "versionType": "git"
            },
            {
              "lessThan": "faf1715798fe72b79e4432ce8c6d03ca69765425",
              "status": "affected",
              "version": "40289e35ca525f29a03989352ab207b6a9675475",
              "versionType": "git"
            },
            {
              "lessThan": "1e76b546e6fca7eb568161f408133904ca6bcf4f",
              "status": "affected",
              "version": "40289e35ca525f29a03989352ab207b6a9675475",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/qcom/qcom_scm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.11"
            },
            {
              "lessThan": "6.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.13",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.2",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Cleanup global \u0027__scm\u0027 on probe failures\n\nIf SCM driver fails the probe, it should not leave global \u0027__scm\u0027\nvariable assigned, because external users of this driver will assume the\nprobe finished successfully.  For example TZMEM parts (\u0027__scm-\u003emempool\u0027)\nare initialized later in the probe, but users of it (__scm_smc_call())\nrely on the \u0027__scm\u0027 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"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "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` \u2014 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 \u2014 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\u0027s own GPU/fastrpc activity.\nS:U - The freed object, the dereferences, and any resulting corruption are all within the kernel\u0027s 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()`\u0027d `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-\u003emempool` (fed to `gen_pool_alloc()`) and `__scm-\u003ecore_clk`/`__scm-\u003epath` (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 \u2014 a NULL/invalid dereference in `qcom_tzmem_alloc()` via `qcom_scm_assign_mem()` \u2014 and use-after-frees reliably panic the kernel even when not weaponized."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:47:11.635Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
        }
      ],
      "title": "firmware: qcom: scm: Cleanup global \u0027__scm\u0027 on probe failures",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-57985",
    "datePublished": "2025-02-27T02:07:09.983Z",
    "dateReserved": "2025-02-27T02:04:28.913Z",
    "dateUpdated": "2026-10-15T21:51:50.141Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.