Trusted Firmware-M up to 2.1.2/2.2.0 on ARM Firmware Upgrade length allocation of resources

Summaryinfo

A vulnerability was found in Trusted Firmware-M up to 2.1.2/2.2.0 on ARM. It has been rated as critical. Impacted is an unknown function of the component Firmware Upgrade Module. This manipulation of the argument length causes allocation of resources. This vulnerability is tracked as CVE-2025-53022. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in Trusted Firmware-M up to 2.1.2/2.2.0 on ARM. Affected by this vulnerability is an unknown function of the component Firmware Upgrade Module. The manipulation of the argument length with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at trustedfirmware.org. This vulnerability is known as CVE-2025-53022 since 06/24/2025. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2.1.3 or 2.2.1 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Firmware Software

Vendor

• Trusted

Name

• Firmware-M

Version

• 2.0
• 2.1
• 2.1.0
• 2.1.1
• 2.1.2
• 2.2.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion