CVE-2023-53428 json
powercap: arm_scmi: Remove recursion while parsing zones
published 2025-09-18 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-29875
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.4.16, 6.5.3, 6.6
- linux Debian 14, Debian 13 6.5.3-1
debian advisories DEBIAN-CVE-2023-53428
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.22.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-syms-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-source-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.18.1
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.22.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.22.1
suse advisories SUSE-SU-2025:4141-1SUSE-SU-2025:4132-1SUSE-SU-2025:4057-1SUSE-SU-2025:20870-1SUSE-SU-2025:20898-1SUSE-SU-2025:3751-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53428 updated
kernel: powercap: arm_scmi: Remove recursion while parsing zones
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
- Technology feeds
References
Sources
- CVE List CVE-2023-53428
- NVD CVE-2023-53428
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.