RISC-V · Security Architecture

AMD Zen 6: A RISC-V Trusted Execution Environment Inside the x86 Security Processor

📅 2026-11-08 ⏱ 9 min read 🔗 Source: linux-firmware.git commit (via Phoronix, 6 November 2026)

The most consequential RISC-V story of the past week did not come from a RISC-V vendor, a summit keynote, or a funding announcement. It came from a single line in a firmware changelog. On 6 November 2026, Michael Larabel of Phoronix flagged a commit to the linux-firmware repository that adds version 4 of the AMD Platform Management Framework (PMF) trusted application for the platform ID 1AH_M80H — the identifier that has been appearing in AMD’s own kernel work for the upcoming Zen 6 client processors. The commit message reads:

“This adds the PMF TA FW v4 for the 1AH_M80H platform. The TA now runs on the RISC-V based TEE, uses a larger shared memory layout and supports an extended set of policy conditions, including up to 20 custom BIOS inputs.”

A RISC-V based Trusted Execution Environment — inside the security processor of a mainstream x86 CPU family. Larabel noted he could not find any other public reference to a RISC-V TEE in an EPYC or Ryzen part. If that holds, the open ISA has just walked through a door that has been held shut by a single Arm core for more than a decade.

What the Commit Actually Establishes

Before extrapolating, it is worth separating the three things the commit message states from everything it leaves open:

Stated in the commitWhat it isConfidence
The PMF TA now runs on a RISC-V based TEEThe trusted application implementing power/thermal policy executes inside a RISC-V-based trusted environment on this platformStated verbatim in the commit message
Larger shared memory layoutThe TA/host interface buffer grows relative to PMF TA v3Stated in the commit message
Up to 20 custom BIOS inputsExtended policy conditions so OEMs can expose more tunables through firmwareStated in the commit message
The whole Secure Processor dropped ArmNot stated — see the unconfirmed list belowUnconfirmed
The platform is Zen 6 / RyzenNot stated — inferred from the 1AH_M80H platform IDInference
Honesty check: the commit never mentions “Zen 6”, “Ryzen” or “AMD” by product name. The Zen 6 association rests on the platform ID: Family 1Ah Model 80h is the identifier AMD’s own kernel work has been using for the next client generation — including k10temp thermal-driver support for Models 80h–8Fh posted in May 2026, and Zen 6 “Olympic Ridge” plus a socketed Medusa1 part for AM5 listed in AMD documentation. That inference is reasonable but it is still an inference.

The Block That Wakes Up First: AMD’s Secure Processor

Every modern Ryzen and EPYC chip carries a small, separate processor that runs before the x86 cores come out of reset. AMD calls it the AMD Secure Processor, formerly the Platform Security Processor (PSP). It verifies firmware at boot, holds keys, runs the firmware TPM, and on server parts manages the memory-encryption machinery behind SEV. For its entire life, that block has been an Arm Cortex-A5 running TrustZone — licensed from Arm, decade after decade.

The Platform Management Framework is one of the workloads living in that secure world. On Linux, the amd-pmf driver talks to the PMF trusted application to apply power and thermal policy — the “Smart PC” logic that adapts a laptop’s behaviour to power source, lid state and sensor input. Version 4 of that TA is what the new firmware blob ships: same job, new environment, a wider policy surface for OEMs.

Not the First: The RISC-V Security-Core Precedents

If AMD has indeed moved at least part of its security stack to RISC-V, it is following a path already walked by other large silicon vendors — each time quietly, each time in the layer most users never see:

VendorWhat moved to RISC-VWhen / status
NVIDIAIn-house Falcon microcontrollers replaced with RISC-V cores; the GPU System Processor (GSP) that now offloads much of the driver stack is RISC-V basedFalcon swap years back; GSP shipping in data-centre GPUs
Google + OpenTitan projectOpen-source silicon root-of-trust built on RISC-V coresOpenTitan launched 2019; deployed in cloud and consumer silicon
AMD (this commit)PMF trusted application inside the Secure Processor now runs on a RISC-V based TEE for platform 1AH_M80Hlinux-firmware commit, 6 November 2026; scope unconfirmed

The motivation is easy to see from AMD’s side of the table: no per-core royalty, freedom to customise the ISA, and an open specification that security auditors can read end to end — the same argument every other vendor made before making the swap.

What Is Not Confirmed

Keep the claim narrow. The commit says the TA runs on “the RISC-V based TEE.” It does not say the entire Secure Processor has dropped Arm. AMD could have added a dedicated RISC-V core for certain trusted applications while keeping the Cortex-A5 for boot and key management, or it could have moved everything over. AMD has not commented, and a firmware blob will not settle it on its own. Larabel could find no other public reference to a RISC-V TEE in an EPYC or Ryzen part — so whether this is new for Zen 6 or simply never mentioned for Zen 5 is itself unclear.

For buyers, nothing changes in daily use. The firmware TPM and Windows 11’s security checks look identical from the outside; this is an internal platform change, not a feature. For security researchers, it is a bigger deal. The PSP has been a recurring target — from the CTS Labs disclosures in 2018 to the 2021 TU Berlin voltage-glitching attack that defeated the secure processor’s integrity checks. A new core, new firmware and possibly a new TEE OS mean a fresh attack surface, and much of the existing research tooling will not carry over.

Why This Matters for RISC-V

The RISC-V ecosystem tracks hardware-lottery milestones carefully: first RVA23-compliant shipping silicon, first server-class parts, first automotive MCU platforms. What this commit represents, if it holds, is a different kind of first: RISC-V inside the security infrastructure of a mainstream, shipping-soon x86 client platform. Not an edge SoC, not an FPGA experiment — the firmware TPM’s neighbour on the next-generation Ryzen die.

It also demonstrates the quiet adoption pattern that has characterised RISC-V’s enterprise incursions all year. NVIDIA did not announce the Falcon swap; researchers found it. OpenTitan published its openness but deployments stayed opaque until auditors looked. AMD’s move — if that is what it is — was found in a git commit, not a press release. The architecture that wins by default rather than by announcement does not need press releases.

What to Watch

Three things will resolve the remaining ambiguity:

1. AMD’s security documentation for the platform. Once AMD publishes the Zen 6 security documentation, the scope question (dedicated RISC-V core vs full PSP replacement) answers itself. 2. A retail chip on a bench. Firmware reverse-engineering of the first Zen 6 parts will settle which TAs live in which environment. 3. Whether EPYC follows. If the RISC-V TEE appears in server silicon, SEV’s trust boundary discussion becomes part of the story — that is where the stakes are highest.

The honest summary: a firmware changelog for an unannounced platform names a RISC-V TEE where a decade of AMD history had only an Arm Cortex-A5. The scope is unconfirmed and AMD is silent. But the sentence exists in a public repository, it was committed by AMD engineers, and it is the first time it has appeared in this family of products. That is enough to make it the most interesting RISC-V data point of the week — and enough to watch what ships in the silicon.

Sources: Phoronix, “A RISC-V Based TEE With AMD Zen 6 CPUs” (6 November 2026); linux-firmware.git commit “amd_pmf: Add AMD PMF TA Firmware v4 for 1AH_M80H”; Hardware Busters analysis (7 November 2026). Commit message quoted verbatim as reproduced by Phoronix.

中文摘要

本周最有分量的 RISC-V 新闻不是来自任何 RISC-V 厂商,而是来自 linux-firmware 仓库的一条提交。2026 年 11 月 6 日,Phoronix 的 Michael Larabel 发现:为平台标识 1AH_M80H(即 AMD 自己内核工作中对应下一代 Zen 6 客户端处理器的 ID)新增的 AMD 平台管理框架(PMF)可信应用 v4 固件,提交说明明确写着「该 TA 现在运行在 基于 RISC-V 的 TEE 上」,同时共享内存布局增大、策略条件扩展(最多 20 个自定义 BIOS 输入项)。

背景:AMD 安全处理器(PSP)负责安全启动、密钥管理、固件 TPM 与服务器侧 SEV 内存加密,十余年来一直由 Arm Cortex-A5 + TrustZone 承担;PMF TA 是其中负责功耗/热策略(Linux amd-pmf 驱动的 Smart PC 逻辑)的可信应用。先例:NVIDIA 多年前已把 Falcon 微控制器换成 RISC-V,GSP 也是 RISC-V;Google OpenTitan 信任根同样基于 RISC-V。

未确认部分(重点):提交未提「Zen 6」字样,关联仅由平台 ID 推断;也未说明整个安全处理器已弃用 Arm——可能是新增专用 RISC-V 核与 Cortex-A5 并存,也可能只接管部分 TA。AMD 未置评。对普通用户无感知;对安全研究者是新攻击面(PSP 曾被 CTS Labs 2018 与 TU Berlin 2021 电压毛刺攻击命中)。若坐实,这是 RISC-V 首次进入主流 x86 客户端平台的安全基础设施层。

Кратко (RU)

Самая значимая новость недели о RISC-V пришла не от вендора, а из репозитория linux-firmware. 6 ноября 2026 года Phoronix (Michael Larabel) заметил коммит, добавляющий доверенное приложение AMD PMF v4 для платформы 1AH_M80H — идентификатора, связанного с готовящимися клиентскими процессорами Zen 6. В описании коммита прямо сказано: «TA теперь работает на TEE на базе RISC-V», с увеличенной общей памятью и расширенным набором условий политики (до 20 пользовательских входов BIOS).

Контекст: защищённый процессор AMD (PSP) более десятилетия строился на Arm Cortex-A5 + TrustZone и отвечает за безопасную загрузку, ключи, firmware TPM и SEV. Прецеденты: NVIDIA давно заменила микроконтроллеры Falcon на RISC-V (и GSP — тоже RISC-V), OpenTitan Google основан на RISC-V.

Не подтверждено: коммит не упоминает «Zen 6» (связь — по ID платформы) и не говорит, что весь PSP отказался от Arm — возможен специальное RISC-V-ядро рядом с Cortex-A5. AMD не комментирует. Для пользователей ничего не меняется; для исследователей безопасности — новая поверхность атаки.

Resumen (ES)

La noticia RISC-V más importante de la semana no vino de un fabricante, sino de un commit en linux-firmware. El 6 de noviembre de 2026, Phoronix (Michael Larabel) señalizó un commit que añade la aplicación confiable AMD PMF v4 para la plataforma 1AH_M80H — el ID asociado a los próximos procesadores cliente Zen 6. El mensaje dice textualmente: «El TA ahora se ejecuta en un TEE basado en RISC-V», con una memoria compartida más grande y hasta 20 entradas BIOS personalizadas.

Contexto: el procesador de seguridad de AMD (PSP) durante más de una década ha sido un Arm Cortex-A5 con TrustZone, responsable del arranque seguro, claves, firmware TPM y SEV. Precedentes: NVIDIA sustituyó sus microcontroladores Falcon por núcleos RISC-V (y el GSP también es RISC-V); el root-of-trust OpenTitan de Google usa RISC-V.

No confirmado: el commit no menciona «Zen 6» (la asociación es por el ID de plataforma) ni que todo el PSP haya abandonado Arm — podría ser un núcleo RISC-V dedicado junto al Cortex-A5. AMD no ha comentado. Para el usuario final nada cambia; para los investigadores de seguridad, es una nueva superficie de ataque.

Résumé (FR)

La nouvelle RISC-V la plus marquante de la semaine ne vient pas d’un fondeur, mais d’un commit dans linux-firmware. Le 6 novembre 2026, Phoronix (Michael Larabel) a repéré un commit ajoutant l’application de confiance AMD PMF v4 pour la plateforme 1AH_M80H — l’identifiant associé aux futurs processeurs clients Zen 6. Le message dit textuellement : « Le TA s’exécute désormais sur un TEE basé sur RISC-V », avec une mémoire partagée agrandie et jusqu’à 20 entrées BIOS personnalisées.

Contexte : le processeur de sécurité d’AMD (PSP) repose depuis plus de dix ans sur un Arm Cortex-A5 avec TrustZone (démarrage sécurisé, clés, firmware TPM, SEV). Précédents : NVIDIA a remplacé ses microcontrôleurs Falcon par des cœurs RISC-V (le GSP aussi est RISC-V) ; OpenTitan de Google repose sur RISC-V.

Non confirmé : le commit ne mentionne pas « Zen 6 » (association par l’ID de plateforme) et ne dit pas que tout le PSP a abandonné Arm — un cœur RISC-V dédié peut coexister avec le Cortex-A5. AMD ne commente pas. Rien ne change pour l’utilisateur ; pour les chercheurs en sécurité, c’est une nouvelle surface d’attaque.

Kurzfassung (DE)

Die gewichtigste RISC-V-Meldung der Woche kam nicht von einem Hersteller, sondern aus einem Commit im linux-firmware-Repository. Am 6. November 2026 meldete Phoronix (Michael Larabel) einen Commit, der die Trusted Application AMD PMF v4 für die Plattform 1AH_M80H hinzufügt — die Kennung, die AMD in eigener Kernel-Arbeit für die kommenden Client-Prozessoren Zen 6 verwendet. Der Commit-Text sagt wörtlich: „Die TA läuft jetzt auf einem RISC-V-basierten TEE“, mit größerem Shared-Memory-Layout und bis zu 20 benutzerdefinierten BIOS-Eingängen.

Kontext: AMDs Secure Processor (PSP) basiert seit über einem Jahrzehnt auf einem Arm Cortex-A5 mit TrustZone (Secure Boot, Schlüssel, Firmware-TPM, SEV). Präzedenzfälle: NVIDIA hat seine Falcon-Mikrocontroller längst durch RISC-V-Kerne ersetzt (auch der GSP ist RISC-V); Googles OpenTitan-Root-of-Trust basiert ebenfalls auf RISC-V.

Unbestätigt: Der Commit erwähnt „Zen 6“ nicht (Zuordnung über die Plattform-ID) und sagt nicht, dass der gesamte PSP Arm aufgegeben hat — ein dedizierter RISC-V-Kern könnte neben dem Cortex-A5 existieren. AMD äußert sich nicht. Für Nutzer ändert sich nichts; für Sicherheitsforscher entsteht eine neue Angriffsfläche.

خلاصه (FA)

مهم‌ترین خبر RISC-V این هفته از یک تولیدکننده نیامد، بلکه از یک کامیت در مخزن linux-firmware آمد. در ۶ نوامبر ۲۰۲۶ فورونیکس (مایکل لارابِل) کامیتی را گزارش کرد که برنامهٔ معتمد AMD PMF نسخهٔ ۴ را برای پلتفرم 1AH_M80H — شناسه‌ای که در کارهای کرنل AMD به نسل آیندهٔ پردازنده‌های کلاینت Zen 6 مربوط است — اضافه می‌کند. متن کامیت تصریح می‌کند: «TA اکنون روی یک TEE مبتنی بر RISC-V اجرا می‌شود»، با حافظهٔ مشترک بزرگ‌تر و تا ۲۰ ورودی BIOS سفارشی.

زمینه: پردازندهٔ امن AMD (PSP) بیش از یک دهه بر پایهٔ Arm Cortex-A5 با TrustZone بوده است (بوت امن، کلیدها، firmware TPM و SEV). پیشینه: NVIDIA مدت‌ها پیش میکروکنترلرهای Falcon را با هسته‌های RISC-V جایگزین کرد (GSP نیز RISC-V است) و OpenTitan گوگل نیز بر RISC-V بنا شده است.

تأییدنشده: کامیت نام «Zen 6» را نمی‌برد (ارتباط از طریق شناسهٔ پلتفرم است) و نمی‌گوید کل PSP از Arm دست کشیده است — ممکن است هستهٔ اختصاصی RISC-V در کنار Cortex-A5 وجود داشته باشد. AMD اظهارنظر نکرده است. برای کاربران چیزی تغییر نمی‌کند؛ برای پژوهشگران امنیتی یک سطح حملهٔ تازه است.