AMD Zen 6 Ryzen processors switch to RISC-V-based trusted execution environment

A linux-firmware.git commit reveals that AMD's upcoming Zen 6 Ryzen client processors, identified as Family 1Ah M80h, use a RISC-V-based Trusted Execution Environment rather than the ARM-based core found in prior generations. The change was discovered in firmware for the AMD Platform Management Framework Trusted Application, which handles power, thermal, and system behavior policies. Previously, AMD's Secure Processor and Platform Security Processor relied on an ARM Cortex-A5 core with ARM TrustZone technology. The new PMF TA firmware version 4 for 1AH_M80H runs on this RISC-V TEE, uses an expanded shared memory layout, and supports up to 20 custom BIOS inputs for policy conditions.

This marks a notable architectural shift for AMD's security subsystem and aligns with broader industry momentum toward RISC-V in embedded and trusted computing roles. The firmware commit indicates Linux support preparation is underway ahead of Zen 6's commercial launch, continuing AMD's pattern of upstreaming platform enablement early.

Architecture and firmware implications

• RISC-V TEE core: The Zen 6 Platform Security Processor replaces the previous ARM Cortex-A5/TrustZone implementation with a RISC-V-based Trusted Execution Environment, representing a new ISA foundation for AMD's security subsystem.
• Expanded shared memory: The new firmware uses a larger shared memory layout between the TEE and host system, enabling more complex policy structures and communication.
• Extended policy conditions: The TA now supports up to 20 custom BIOS inputs for configuring platform behavior, an increase in flexibility for OEM and system integrator customization.
• Family 1Ah M80H identification: The linux-firmware.git commit explicitly targets this AMD processor family, confirming the RISC-V TEE applies to upcoming Zen 6 client processors rather than server EPYC parts.

Why it matters

AMD's migration from ARM to RISC-V for its security processor reduces licensing dependencies and may simplify long-term firmware maintenance for a core component present in every Ryzen system. For Linux distributions and system firmware developers, this shift requires updated tooling and validation for RISC-V TEE firmware loading and attestation, though AMD's early upstreaming to linux-firmware.git suggests the transition will be transparent to end users by launch. The move also reinforces RISC-V's credibility in high-volume commercial silicon beyond embedded microcontrollers, potentially accelerating open-source security firmware efforts around RISC-V trusted computing standards.