CVE-2024-50159 (GCVE-0-2024-50159)

Vulnerability from cvelistv5 – Published: 2024-11-07 09:31 – Updated: 2026-08-05 11:42
VLAI
Title
firmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup()
Summary
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup() Clang static checker(scan-build) throws below warning: | drivers/firmware/arm_scmi/driver.c:line 2915, column 2 | Attempt to free released memory. When devm_add_action_or_reset() fails, scmi_debugfs_common_cleanup() will run twice which causes double free of 'dbg->name'. Remove the redundant scmi_debugfs_common_cleanup() to fix this problem.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329 , < 6d91d07913aee90556362d648d6a28a1eda419dc (git)
Affected: c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329 , < fb324fdaf546bf14bc4c17e0037bca6cb952b121 (git)
Affected: c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329 , < 39b13dce1a91cdfc3bec9238f9e89094551bd428 (git)
Create a notification for this product.
Linux Linux Affected: 6.3
Unaffected: 0 , < 6.3 (semver)
Unaffected: 6.6.59 , ≤ 6.6.* (semver)
Unaffected: 6.11.6 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/arm_scmi/driver.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6d91d07913aee90556362d648d6a28a1eda419dc",
              "status": "affected",
              "version": "c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329",
              "versionType": "git"
            },
            {
              "lessThan": "fb324fdaf546bf14bc4c17e0037bca6cb952b121",
              "status": "affected",
              "version": "c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329",
              "versionType": "git"
            },
            {
              "lessThan": "39b13dce1a91cdfc3bec9238f9e89094551bd428",
              "status": "affected",
              "version": "c3d4aed763ce4a39f8ed36c7b7cd9a6a35971329",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/arm_scmi/driver.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.3"
            },
            {
              "lessThan": "6.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.59",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.59",
                  "versionStartIncluding": "6.3",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.6",
                  "versionStartIncluding": "6.3",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "6.3",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup()\n\nClang static checker(scan-build) throws below warning\uff1a\n  |  drivers/firmware/arm_scmi/driver.c:line 2915, column 2\n  |        Attempt to free released memory.\n\nWhen devm_add_action_or_reset() fails, scmi_debugfs_common_cleanup()\nwill run twice which causes double free of \u0027dbg-\u003ename\u0027.\n\nRemove the redundant scmi_debugfs_common_cleanup() to fix this problem."
        }
      ],
      "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 defect lives in the `arm-scmi` platform driver\u0027s `scmi_probe()` debugfs setup path, which is only executed during local device/driver binding \u2014 there is no network, packet, or remote-peer input anywhere on the path. Reaching it requires local system context (boot, module load, or deferred-probe retry), so Local is the appropriate vector.\nAC:H - The double free is only reached when `__devres_alloc_node()` returns NULL, i.e. a small GFP_KERNEL allocation fails at one exact instant during a one-shot probe; small GFP_KERNEL allocations reclaim or OOM-kill rather than fail, and `.suppress_bind_attrs = true` removes any sysfs re-probe retry loop. The attacker cannot initiate the probe nor steer that specific allocation, so success depends on conditions genuinely outside their control, compounded by the non-default `CONFIG_ARM_SCMI_RAW_MODE_SUPPORT`/`CONFIG_ARM_SCMI_DEBUG_COUNTERS` requirement.\nPR:L - The only attacker-influenceable ingredient is system memory pressure, which an ordinary unprivileged local process can generate without any capability, and SCMI probe can occur after userspace is up via udev-driven module load or deferred-probe retry. Choosing the higher-severity option over PR:H, which would otherwise apply since deliberately initiating a probe needs CAP_SYS_MODULE.\nUI:N - Driver probe and the debugfs setup run autonomously from the DT/platform-device match; no victim must open a file, mount a filesystem, or take any other action. The error path executes purely as a consequence of the allocation failure.\nS:U - The double free corrupts the kernel\u0027s own slab allocator and dentry cache within the same kernel security authority. No hypervisor, IOMMU, container, or sandbox boundary is crossed.\nC:H - A slab double free lets the same object be handed out to two independent allocations, and the redundant `debugfs_remove_recursive()` additionally dereferences a released dentry \u2014 both are read primitives over attacker-unrelated kernel objects. Consistent with treating use-after-free/double-free as enabling arbitrary kernel memory disclosure.\nI:H - Freeing `dbg-\u003ename` and `dbg-\u003etype` twice corrupts the SLUB freelist, the standard stepping stone to aliased-object and arbitrary-write primitives, and the stale dentry is written through by the second recursive removal. Memory corruption of this class is scored as enabling control-flow hijacking.\nA:H - With freelist hardening the second `kfree()` raises a BUG/panic outright; without it, freelist corruption and the dentry use-after-free reliably lead to an oops during subsequent allocation or dcache activity. Either outcome is a full kernel crash."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:42:09.468Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6d91d07913aee90556362d648d6a28a1eda419dc"
        },
        {
          "url": "https://git.kernel.org/stable/c/fb324fdaf546bf14bc4c17e0037bca6cb952b121"
        },
        {
          "url": "https://git.kernel.org/stable/c/39b13dce1a91cdfc3bec9238f9e89094551bd428"
        }
      ],
      "title": "firmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50159",
    "datePublished": "2024-11-07T09:31:36.167Z",
    "dateReserved": "2024-10-21T19:36:19.961Z",
    "dateUpdated": "2026-08-05T11:42:09.468Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50159",
      "date": "2026-11-19",
      "epss": "0.00224",
      "percentile": "0.1315"
    },
    "microsoft_vex": {
      "current_release_date": "2026-02-18T14:10:13.000Z",
      "cve": "CVE-2024-50159",
      "id": "msrc_CVE-2024-50159",
      "initial_release_date": "2025-01-29T00:00:00.000Z",
      "product_status:fixed": "2",
      "product_status:known_affected": "2",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "firmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup()",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2024-50159.json",
      "version": "2"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-05T13:09:38+00:00",
      "cve": "CVE-2024-50159",
      "id": "CVE-2024-50159",
      "initial_release_date": "2024-11-07T00:00:00+00:00",
      "product_status:known_not_affected": "199",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: firmware: arm_scmi: Fix the double free in scmi_debugfs_common_setup()",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50159.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.