Shell crash via unbounded function recursion
Published Jul 15, 2026 · Updated Jul 15, 2026
Uncontrolled recursion in BusyBox 0.52 through 1.38.0 allows local users to crash the ash shell with a recursive shell function. The evalfun() path repeatedly enters recursive shell functions without tracking call depth, exhausting the process stack instead of rejecting excessive nesting. Exploitation requires local ability to run crafted ash input and interrupts only the affected shell process, with no reported data disclosure or modification.
Summary
What happened
Uncontrolled recursion in BusyBox 0.52 through 1.38.0 allows local users to crash the ash shell with a recursive shell function. The evalfun() path repeatedly enters recursive shell functions without tracking call depth, exhausting the process stack instead of rejecting excessive nesting. Exploitation requires local ability to run crafted ash input and interrupts only the affected shell process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2026-38755
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, CWE-674, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo