← Back

Trusted Firmware M

trusted_firmware-m

Vendor: Arm • 4 CVEs

CVEs (4)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
2Arm
Trustedfirmware
2Trusted Firmware M
Trusted Firmware M
Jun 17, 2026
Sep 5, 2024
N/A· v4
4.7 MEDIUM· v3
N/A· v2
An issue was discovered in Trusted Firmware-M through 2.0.0. The lack of argument verification in the logging subsystem allows attackers to read sensitive data via the login function.
2Arm
Trustedfirmware
2Trusted Firmware M
Trusted Firmware M
Jun 17, 2026
Sep 8, 2023
N/A· v4
7.5 HIGH· v3
N/A· v2
In Trusted Firmware-M through TF-Mv1.8.0, for platforms that integrate the CryptoCell accelerator, when the CryptoCell PSA Driver software Interface is selected, and the Authenticated Encryption with Associated Data Chac...Show more
In Trusted Firmware-M through TF-Mv1.8.0, for platforms that integrate the CryptoCell accelerator, when the CryptoCell PSA Driver software Interface is selected, and the Authenticated Encryption with Associated Data Chacha20-Poly1305 algorithm is used, with the single-part verification function (defined during the build-time configuration phase) implemented with a dedicated function (i.e., not relying on usage of multipart functions), the buffer comparison during the verification of the authentication tag does not happen on the full 16 bytes but just on the first 4 bytes, thus leading to the possibility that unauthenticated payloads might be identified as authentic. This affects TF-Mv1.6.0, TF-Mv1.6.1, TF-Mv1.7.0, and TF-Mv1.8.Show less
2Arm
Trustedfirmware
2Trusted Firmware M
Trusted Firmware M
Jun 17, 2026
Mar 1, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
Trusted Firmware M 1.4.x through 1.4.1 has a buffer overflow issue in the Firmware Update partition. In the IPC model, a psa_fwu_write caller from SPE or NSPE can overwrite stack memory locations.
2Arm
Trustedfirmware
2Trusted Firmware M
Trusted Firmware M
Jun 17, 2026
May 25, 2021
N/A· v4
5.5 MEDIUM· v3
4.9 MEDIUM· v2
In Arm Trusted Firmware M through 1.2, the NS world may trigger a system halt, an overwrite of secure data, or the printing out of secure data when calling secure functions under the NSPE handler mode.