Read the docs

MCUboot TinyCrypt AES-CTR backend leaves AES key schedule in memory after boot

Priority LOW 9CWE-226Published · Updated

Key facts

Attack vector
Physical
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

With the TinyCrypt backend (MCUBOOT_USE_TINYCRYPT), bootutil_aes_ctr_drop() in aes_ctr_tinycrypt.h was an empty stub, so the AES-128 key schedule was never cleared. After an encrypted upgrade in single-image builds, boot_state_clear() leaves the image content-encryption key schedule in boot_data, and boot_decrypt_key() leaves the key-encryption key schedule on the stack. The first round key equals the cipher key, so an attacker who can read leftover RAM, through debug access or code running later on the device, can recover the content key and decrypt the image. The long-term private decryption key and image authenticity are not affected, and the weakness is CWE-226.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

When MCUboot is built with the TinyCrypt crypto backend (MCUBOOT_USE_TINYCRYPT), bootutil_aes_ctr_drop() in boot/bootutil/include/bootutil/crypto/aes_ctr_tinycrypt.h was an empty stub. The AES-CTR context for this backend is the fully expanded AES-128 key schedule (struct tc_aes_key_sched_struct). Generic code relies on this hook to release and clear key state, so with TinyCrypt nothing was cleared. The mbedTLS and PSA backends do free or destroy their key state here. As a result, boot_state_clear(), which boot_go() calls before handing off to the application, left the image's AES content-encryption key schedule in the static boot_data state. This is the case after an encrypted upgrade in single-image builds, where boot_enc_zeroize() is not called. boot_decrypt_key() likewise left the ECIES-derived key-encryption key schedule on the stack. The affected build uses MCUBOOT_ENC_IMAGES with TinyCrypt, which is the default ECDSA and Ed25519 backend in the Zephyr port. The first AES-128 round key equals the cipher key, so anyone who can read the leftover bootloader RAM after boot can recover the image content key and decrypt that encrypted image. That includes a physical attacker with debug or RAM access, or code later running on the device. This weakens image-encryption key confidentiality (and so the confidentiality of the encrypted image's plaintext). The device's long-term private decryption key is not exposed, and image authenticity is not affected. The fix wipes the context with bootutil_wipe_memory().

Why it matters now

EPSS 0.00083 0th percentileScored 2026-11-16
Fix Fixed mcuboot (mcu-tools): 2.5.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
mcu-toolsmcuboot1.3.0 to before 2.5.02.5.0Patch availableCNA
  • mcuboot Vendormcu-tools Affected 1.3.0 to before 2.5.0 Fixed in 2.5.0 Patch available CNA

Remediation

Upgrade MCUboot to 2.5.0 or later. The fix calls bootutil_wipe_memory() on the AES-CTR context in bootutil_aes_ctr_drop().

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA mcuboot (mcu-tools) Fixed in 2.5.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    mcu-tools mcuboot 2.5.0

    7 records Highest priority Priority LOW 7 LOW

    Other records, highest priority first

    • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image uploadPriority LOW 17
    • TI-2026-91078 Out-of-bounds read in MCUboot image hash during validationPriority LOW 13
    • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512Priority LOW 13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-128091

References

  • TI-2024-21755 MCUboot Injection attack of unprotected TLV values CVSS 3.1HIGH 7.7
  • TI-2026-91073 Out-of-bounds read in MCUboot serial recovery image index CVSS 3.1MEDIUM 5.1
  • TI-2026-91071 NULL pointer dereference in MCUboot serial recovery image upload CVSS 3.1MEDIUM 4.0
  • TI-2026-91078 Out-of-bounds read in MCUboot image hash during validation CVSS 3.1LOW 2.9
  • TI-2026-91074 MCUboot split-image out-of-bounds stack write with SHA-384/SHA-512 CVSS 3.1LOW 2.9
  • TI-2026-91072 Uninitialised stack memory leaks into MCUboot measured-boot record CVSS 3.1LOW 2.4
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences