Security readout for executives and security teams
Plain-English summary
A Linux ARM SCMI driver error can free the same memory twice during a failed debugfs setup. This may crash the kernel or potentially compromise system integrity and confidentiality. The published CVSS score is 7.0, but triggering requires local access, privileges, high complexity, and a specific failure path.
Executive priority
Treat this as a high-priority kernel maintenance issue for confirmed ARM SCMI deployments, especially critical infrastructure. It is not supported as an internet-wide emergency because the documented attack vector is local, complexity is high, and active exploitation is unconfirmed. Validate exposure before accelerating disruptive updates.
Technical view
If devm_add_action_or_reset() fails in scmi_debugfs_common_setup(), cleanup executes twice and double-frees dbg->name. The correction removes the redundant scmi_debugfs_common_cleanup() call. Clang scan-build identified the defect. The supplied version data names Linux 6.3, 6.6.59, 6.11.6, and 6.12, but does not clearly express complete affected ranges.
Likely exposure
Exposure appears limited to systems running affected Linux kernels with the ARM SCMI firmware driver and relevant debugfs setup path. The CVSS vector indicates a local, low-privileged attacker and high attack complexity. The bundle does not establish exposure on non-ARM systems, internet reachability, or reliable attacker control of the required failure.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active or public exploitation. It describes a static-analysis finding in an uncommon error path. Although the CVSS assessment allows severe confidentiality, integrity, and availability impact, practical exploitability is not demonstrated by these sources.
Researcher notes
The vulnerable behavior depends on devm_add_action_or_reset() failing after cleanup registration causes an immediate reset action; an additional explicit cleanup then releases dbg->name again. The source bundle does not provide a CWE, proof of exploitation, complete version-range semantics, or distribution-specific package status. Use vendor backport information to determine remediation accurately.
Mitigation direction
- Inventory ARM systems using the Linux SCMI firmware driver.
- Compare installed kernels against vendor advisories and the linked stable fixes.
- Upgrade to a vendor-supported kernel containing the applicable correction.
- Restrict local access and unnecessary privileges until affected systems are updated.
- Prioritize externally important or safety-sensitive ARM infrastructure.
Validation and detection
- Record kernel versions and architectures across potentially exposed systems.
- Confirm whether the ARM SCMI firmware driver is present or enabled.
- Verify the installed kernel includes the applicable linked fix commit.
- Review kernel logs for crashes or memory errors involving ARM SCMI setup.
- Retest SCMI initialization after updating the kernel.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-50159 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/6d91d07913aee90556362d648d6a28a1eda419dcCVE reference, Linux
- https://git.kernel.org/stable/c/fb324fdaf546bf14bc4c17e0037bca6cb952b121CVE reference, Linux
- https://git.kernel.org/stable/c/39b13dce1a91cdfc3bec9238f9e89094551bd428CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.