CVE-2023-53428: powercap: arm_scmi: Remove recursion while parsing zones
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3e767d6850f867cc33ac16ca097350a1d2417982, 8022b64fb7daa6135d9f7b0e2f7b5b8e9e5179c9, b427c23cebc5c926516f20304bf1acc05a33d147.
Low priority for now. Upgrade to Linux Linux 3e767d6850f867cc33ac16ca097350a1d2417982, 8022b64fb7daa6135d9f7b0e2f7b5b8e9e5179c9, b427c23cebc5c926516f20304bf1acc05a33d147 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-674
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2 and later · before 6.4.16
- linux linux kernel6.5 and later · before 6.5.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.2affected
- b55eef5226b71edf5422de246bc189da1fdc9000 and later · before b427c23cebc5c926516f20304bf1acc05a33d147affected · git
- b55eef5226b71edf5422de246bc189da1fdc9000 and later · before 8022b64fb7daa6135d9f7b0e2f7b5b8e9e5179c9affected · git
- b55eef5226b71edf5422de246bc189da1fdc9000 and later · before 3e767d6850f867cc33ac16ca097350a1d2417982affected · git
- before 6.2not affected · semver
- 6.4.16 and later · up to and including 6.4.*not affected · semver
- 6.5.3 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53426Sep 18, 2025 · xsk: Fix xsk_diag use-after-free error during socket cleanup31Monitor
- ← EarlierCVE-2023-53427Sep 18, 2025 · cifs: Fix warning and UAF when destroy the MR list31Monitor
- Later →CVE-2023-53430Sep 18, 2025 · wifi: mt76: dma: fix memory leak running mt76_dma_tx_cleanup22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3e767d6850f867cc33ac16ca097350a1d2417982 | Vendor (CNA) |
| Linux Linux | 8022b64fb7daa6135d9f7b0e2f7b5b8e9e5179c9 | Vendor (CNA) |
| Linux Linux | b427c23cebc5c926516f20304bf1acc05a33d147 | Vendor (CNA) |
| debian:linux | 6.5.3-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-43185230 days apartksmbd: fix signededness bug in smb_direct_prepare_negotiation()39Monitor
- CVE-2025-3845955 days apartatm: clip: Fix infinite recursive call of clip_push().31Monitor
- CVE-2026-53202280 days apartaccel/ivpu: Fix signed integer truncation in IPC receive31Monitor
- CVE-2026-53267280 days apartnetfilter: nft_ct: bail out on template ct in get eval31Monitor
- CVE-2024-35886487 days apartipv6: Fix infinite recursion in fib6_dump_done().31Monitor
- CVE-2026-53395304 days apartnfsd: fix dead ACL conflict guard in nfsd4_create30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.