Trusted Firmware-M in Zephyr firmware: identifiers and CRA notes

What it is

Trusted Firmware-M

• Homepage
• Repository

Notes on this component

Trusted Firmware-M, surfaced from a `.config`-only upload where no west module was listed; it is skipped once the `trusted-firmware-m` module is already in the inventory. `menuconfig BUILD_WITH_TFM` lives in Zephyr's `modules/trusted-firmware-m/Kconfig.tfm` and is set on any Zephyr+TF-M build, on any vendor's board, so this row names the upstream project, not Nordic's fork. Unlike most NCS rows this one has a CPE, so TF-M's own CVEs do match: they include CVE-2023-40271 (with the CryptoCell PSA driver, the ChaCha20-Poly1305 tag check compared 4 bytes instead of 16, affecting 1.6.0 to 1.8.0), CVE-2021-43619 (a stack buffer overflow in the Firmware Update partition, affecting 1.4.0 to 1.4.1) and CVE-2023-51712 (missing argument checks in the logging subsystem leak secure data, through 2.0.0). Matching is an approximation: an nRF Connect SDK build uses Nordic's fork of TF-M (nrfconnect/sdk-trusted-firmware-m), which can carry a fix the upstream version number does not show. Identity changed from the Nordic fork to upstream on 11 October 2026.

Where it hides in a firmware SBOM

It is compiled into the kernel image when CONFIG_BUILD_WITH_TFM is y. It does not appear in west spdx output; the only trace is the .config file in your build directory.

The identifiers we assign

PURLpackage URL: a standard way to name a software package

pkg:generic/trustedfirmware/trusted-firmware-m@{version}

CPEthe product name vulnerability databases use to say what a flaw affects

cpe:2.3:o:trustedfirmware:trusted_firmware-m:{version}:*:*:*:*:*:*:*

{version} is filled in from your build. The version is read from the version your SBOM already carries for it.

The SBOM check adds these identifiers to a component your build listed without them.

Honest gaps

Vendor: trustedfirmware.

Where this row comes from

https://github.com/zephyrproject-rtos/zephyr/blob/v4.4.0/modules/trusted-firmware-m/Kconfig.tfm
Checked on 11 October 2026.

Known vulnerabilities

Not checked yet

Vulnerability data changes daily. Check the version you ship in the SBOM check.

CRA notes

• List this component in your SBOM. Annex I, Part II (1): Identify and document components and vulnerabilities, including an SBOMKnow what is in your product. Identify and document its components and their vulnerabilities, including by producing a software bill of materials (SBOM) in a common machine-readable format that covers at least the top-level dependencies.
• Ship the version with no known exploitable vulnerabilities at release. Annex I, Part I (2(a)): Made available without known exploitable vulnerabilitiesWhen you place a release on the market, it must not ship with known vulnerabilities that can be exploited in your product. "Exploitable" means an attacker could effectively use it under practical operating conditions (Article 3(41)), not only in theory or in a lab. The Commission's draft guidance (C(2026) 5252, points 231 to 237; a draft, not binding) gives three ways a vulnerability is "known". One: it is listed in a relevant public vulnerability database, such as the European vulnerability database (EUVD) or another prominent one. Two: you learned of it from information that is not public, for example a security researcher's coordinated disclosure or your own testing and analysis; a vulnerability you know about and have not disclosed still counts. Three: it has been publicly and prominently reported in reliable media, whether specialist security publications or general news. A report is not yet proof: it does not by itself mean the vulnerability can be exploited in practice or applies to your product, so investigate promptly and confirm whether it does. A limited time may pass between the first report and that confirmation. If a vulnerability becomes known shortly before release, you decide from your cybersecurity risk assessment whether the release can go out or the vulnerability must be fixed first. Weigh its severity, exploitability and potential impact, and the risks to the product once in use; you may also weigh the risks of delaying the release, for example because it fixes other exploitable vulnerabilities. After release, the Part II vulnerability handling requirements still apply. Check your components against vulnerability databases before each release, and fix or justify what you find.

Source: Annex I of Regulation (EU) 2024/2847 (Cyber Resilience Act), legal state 2026.10.13-1.

Related Zephyr components

No related components yet.

Guides that mention Trusted Firmware-M

• The CRA for Zephyr developers: what the law asks, what west spdx gives you, and what is left

Next step

Declarable prepares documentation for you to review. It is not legal advice and not certification. You sign your own declaration of conformity.