CVE-2023-53428: powercap: arm_scmi: Remove recursion while parsing zones
In the Linux kernel, the following vulnerability has been resolved:
powercap: arm_scmi: Remove recursion while parsing zones
Powercap zones can be defined as arranged in a hierarchy of trees and when
registering a zone with powercap_register_zone(), the kernel powercap
subsystem expects this to happen starting from the root zones down to the
leaves; on the other side, de-registration by powercap_deregister_zone()
must begin from the leaf zones.
Available SCMI powercap zones are retrieved dynamically from the platform
at probe time and, while any defined hierarchy between the zones is
described properly in the zones descriptor, the platform returns the
availables zones with no particular well-defined order: as a consequence,
the trees possibly composing the hierarchy of zones have to be somehow
walked properly to register the retrieved zones from the root.
Currently the ARM SCMI Powercap driver walks the zones using a recursive
algorithm; this approach, even though correct and tested can lead to kernel
stack overflow when processing a returned hierarchy of zones composed by
particularly high trees.
Avoid possible kernel stack overflow by substituting the recursive approach
with an iterative one supported by a dynamically allocated stack-like data
structure.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53428 is a Linux kernel availability issue in the ARM SCMI powercap driver. A deeply nested platform-reported powercap zone hierarchy can make the kernel use too much stack during probing, potentially causing a kernel crash. The evidence points to local, low-privilege impact on availability only, not data theft or code execution.
Executive priority
Treat this as a moderate infrastructure availability risk. It is not described as remotely exploitable or actively exploited in the provided sources, but affected ARM Linux systems could crash under the vulnerable condition. Patch through normal kernel maintenance, prioritizing systems where downtime matters.
Technical view
The ARM SCMI powercap driver recursively walked dynamically returned powercap zone trees. Because platforms can return very tall hierarchies in undefined order, recursion could overflow the kernel stack. The fix replaces recursion with an iterative walk using a dynamically allocated stack-like structure. CVSS 3.1 is 5.5, AV:L/PR:L/UI:N, availability high.
Likely exposure
Exposure is most likely on Linux systems using ARM SCMI powercap functionality, especially ARM platforms where firmware exposes hierarchical powercap zones. The source bundle names Linux kernel versions and stable commits, but does not provide distribution package mappings or device-specific exposure lists.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The attack model is local with low privileges and no user interaction. Practical exploitability likely depends on platform SCMI powercap zone data and affected kernel code being present.
Researcher notes
Focus review on ARM SCMI powercap zone registration paths and kernel versions before the stable fixes. The vulnerability is CWE-674 recursion-related stack exhaustion. Evidence does not establish confidentiality or integrity impact, exploit availability, or a universal affected-device list.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes and package names.
Prioritize ARM systems using SCMI powercap features for remediation review.
Track the listed kernel stable commits during patch validation.
If no update is available, follow vendor guidance for interim risk reduction.
Validation and detection
Inventory Linux kernel versions on ARM SCMI-capable systems.
Confirm whether the ARM SCMI powercap driver is present and used.
Verify the running kernel includes one of the referenced stable fixes or a backport.
Map distribution package versions to the upstream fixed commits.
Run normal availability regression tests after kernel update in staging.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · low confidence lookup
CWE-674: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.