CVE-2026-26399: n/a
A stack-use-after-return issue exists in the Arduino_Core_STM32 library prior to version 1.7.0. The pwm_start() function allocates a TIM_HandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function returns, interrupt service routines may dereference this dangling pointer, resulting in memory corruption.
AI Analysis
Technical Summary
This vulnerability involves a stack-use-after-return condition in the Arduino_Core_STM32 library's pwm_start() function. The function allocates a TIM_HandleTypeDef structure on the stack and passes its pointer to HAL initialization routines, which store it in a global timer handle registry. Once pwm_start() returns, the stack memory is no longer valid, but interrupt service routines may still access this dangling pointer, leading to potential memory corruption. The CVSS 3.1 base score is 5.3 (medium severity), reflecting local attack vector, low complexity, low privileges required, no user interaction, and impacts on confidentiality, integrity, and availability at a low level. No official patch or remediation guidance is currently available.
Potential Impact
Exploitation of this vulnerability can lead to memory corruption due to dereferencing a dangling pointer by interrupt service routines. This may result in unpredictable behavior, including potential crashes or compromised system stability. The impact affects confidentiality, integrity, and availability at a low level. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid using vulnerable versions of the Arduino_Core_STM32 library or implement additional safeguards to prevent interrupt routines from accessing the invalid pointer. Monitor vendor communications for updates regarding patches or official mitigations.
CVE-2026-26399: n/a
Description
A stack-use-after-return issue exists in the Arduino_Core_STM32 library prior to version 1.7.0. The pwm_start() function allocates a TIM_HandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function returns, interrupt service routines may dereference this dangling pointer, resulting in memory corruption.
CVSS v3.1
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves a stack-use-after-return condition in the Arduino_Core_STM32 library's pwm_start() function. The function allocates a TIM_HandleTypeDef structure on the stack and passes its pointer to HAL initialization routines, which store it in a global timer handle registry. Once pwm_start() returns, the stack memory is no longer valid, but interrupt service routines may still access this dangling pointer, leading to potential memory corruption. The CVSS 3.1 base score is 5.3 (medium severity), reflecting local attack vector, low complexity, low privileges required, no user interaction, and impacts on confidentiality, integrity, and availability at a low level. No official patch or remediation guidance is currently available.
Potential Impact
Exploitation of this vulnerability can lead to memory corruption due to dereferencing a dangling pointer by interrupt service routines. This may result in unpredictable behavior, including potential crashes or compromised system stability. The impact affects confidentiality, integrity, and availability at a low level. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid using vulnerable versions of the Arduino_Core_STM32 library or implement additional safeguards to prevent interrupt routines from accessing the invalid pointer. Monitor vendor communications for updates regarding patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-02-16T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e6665f19fe3cd2cd1d0afd
Added to database: 4/20/2026, 5:46:07 PM
Last enriched: 4/28/2026, 5:48:25 AM
Last updated: 6/4/2026, 3:02:50 AM
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.