Memory corruption via dangling PWM timer handle
Published Apr 20, 2026 · Updated Apr 20, 2026
Stack-use-after-return in Arduino_Core_STM32 before 1.7.0 allows local users to corrupt memory through PWM timer initialization. The pwm_start() function creates a TIM_HandleTypeDef on its stack and lets HAL initialization retain its address in the global timer registry, leaving interrupt handlers to dereference an invalid object after return. Reachability requires firmware built with the affected core and a path that lets attacker-controlled input influence stack reuse and interrupt timing; the bounded result is memory corruption, including a crash or HardFault.
Summary
What happened
Stack-use-after-return in Arduino_Core_STM32 before 1.7.0 allows local users to corrupt memory through PWM timer initialization. The pwm_start() function creates a TIM_HandleTypeDef on its stack and lets HAL initialization retain its address in the global timer registry, leaving interrupt handlers to dereference an invalid object after return. Reachability requires firmware built with the affected core and a path that lets attacker-controlled input influence stack reuse and interrupt timing; the bounded result is memory corruption, including a crash or HardFault.
The record
- CVE
- CVE-2026-26399
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-562
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 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
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