CVE-2025-53022: High severity TrustedFirmware Trusted Firmware-m vulnerability
TrustedFirmware-M (aka Trusted Firmware for M profile Arm CPUs) before 2.1.3 and 2.2.x before 2.2.1 lacks length validation during a firmware upgrade. While processing a new image, the Firmware Upgrade (FWU) module does not validate the length field of the Type-Length-Value (TLV) structure for dependent components against the maximum allowed size. If the length specified in the TLV exceeds the size of the buffer allocated on the stack, the FWU module will overwrite the buffer (and potentially other stack data) with the TLV's value content. An attacker could exploit this by crafting a malicious TLV entry in the unprotected section of the MCUBoot upgrade image. By setting the length field to exceed the expected structure size, the attacker can manipulate the stack memory of the system during the upgrade process.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53022?
CVE-2025-53022 is classified as a high severity vulnerability due to its potential to allow firmware upgrade manipulation.
How do I fix CVE-2025-53022?
To fix CVE-2025-53022, update Trusted Firmware-M to version 2.1.3 or 2.2.1 or later.
What types of systems are affected by CVE-2025-53022?
CVE-2025-53022 affects systems using Trusted Firmware-M versions before 2.1.3 and 2.2.0 before 2.2.1.
What is the impact of CVE-2025-53022?
The impact of CVE-2025-53022 includes potential unauthorized access and corruption of firmware during the upgrade process.
Does CVE-2025-53022 require authentication to exploit?
CVE-2025-53022 can be exploited without authentication, thus posing a significant risk to vulnerable systems.