Device crash via undersized main-thread stack
Published May 1, 2026 · Updated May 1, 2026
Stack exhaustion in Flipper Zero firmware commit ad2a800 allows attackers to crash the device through a configuration-dependent update call chain. The linker script reserves 1,024 bytes for the main thread, while static analysis estimates a 1,464-byte worst-case call chain through firmware-update manifest parsing. The public evidence identifies no attacker-controlled trigger and demonstrates static analysis rather than a runtime crash, so exploitability beyond configuration-dependent device failure remains unverified.
Summary
What happened
Stack exhaustion in Flipper Zero firmware commit ad2a800 allows attackers to crash the device through a configuration-dependent update call chain. The linker script reserves 1,024 bytes for the main thread, while static analysis estimates a 1,464-byte worst-case call chain through firmware-update manifest parsing. The public evidence identifies no attacker-controlled trigger and demonstrates static analysis rather than a runtime crash, so exploitability beyond configuration-dependent device failure remains unverified.
The record
- CVE
- CVE-2026-30363
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Static stack-usage proof of conceptproof of concept · unverified
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