Out-of-bounds stack write via unchecked TLV length
Published Jul 30, 2025 · Updated Jul 30, 2025
Out-of-bounds write in Trusted Firmware-M before 2.1.3 and 2.2.0 allows attackers to corrupt stack memory via a crafted MCUBoot image. The FWU partition's fwu_bootloader_install_image() function copies an image-dependency TLV payload into a stack buffer without checking its length against the expected structure size. The FWU partition must be enabled and process the malicious upgrade image; the overwrite can corrupt adjacent stack data and redirect program execution.
Summary
What happened
Out-of-bounds write in Trusted Firmware-M before 2.1.3 and 2.2.0 allows attackers to corrupt stack memory via a crafted MCUBoot image. The FWU partition's fwu_bootloader_install_image() function copies an image-dependency TLV payload into a stack buffer without checking its length against the expected structure size. The FWU partition must be enabled and process the malicious upgrade image; the overwrite can corrupt adjacent stack data and redirect program execution.
The record
- CVE
- CVE-2025-53022
- Published
- Jul 30, 2025
- Updated
- Jul 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, T1601.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2025CVE publishedPublication date reported by the CVE source.
- Jul 30, 2025Record 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.
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