It is a firmware plumbing change, not a product launch, and the details are thin. What it does and doesn't show is worth separating out.
What AMD actually committed
AMD engineer Shyam Sundar S K authored and signed off the commit. The commit is titled "amd_pmf: Add AMD PMF TA Firmware v4 for 1AH_M80H." The commit message says the trusted application (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.
The change touches two files. It adds a new binary under the amdtee/ directory and updates the repository's WHENCE file, which records firmware provenance and licensing. The author timestamp is November 6, 2026, 21:39 +0530, and the full commit ID is c1c76b61ec873aa3145314b6c0273be93ab45596.
The commit message gives these concrete changes:
- The firmware is version 4 of the PMF trusted application, for the platform identifier 1AH_M80H.
- The TA runs on a RISC-V-based TEE.
- Its shared-memory layout is larger.
- It supports more policy conditions, with a ceiling of 20 custom BIOS inputs.
Where Zen 6 enters the story
The commit never says "Zen 6" or "Ryzen." Phoronix supplies that link. Michael Larabel reads Family 1Ah Model 80h as the upcoming AMD Ryzen Zen 6 client processors.
Independent coverage points the same way. One outlet reported that Linux 7.3 added Zen 6 client support with HSMP and PMF updates, and that the changes specifically identify Family 1Ah Model 80H processors associated with the Zen 6 generation. The Zen 6 tie is therefore well supported circumstantially. It is still an inference from platform naming, not an AMD statement.
Why a RISC-V TEE is notable
Phoronix notes that the AMD Secure Processor / Platform Security Processor (PSP) was traditionally based on the Arm Cortex-A5 core with Arm TrustZone technology. A RISC-V-based TEE is a departure from that description.
Phoronix hedges the finding itself. The site says this is either a new Zen 6 feature or something that wasn't widely reported on for recent Zen 5 processors. It also says it found no other references to a RISC-V TEE or core in EPYC or Ryzen parts. I couldn't find any either.
The commit does not establish several things, so don't read them into it:
- It does not say the x86 cores are changing. Zen 6 CPUs stay x86, and nothing here suggests Windows or Linux could run RISC-V code on them.
- It does not say that RISC-V is replacing Arm across AMD's lineup, or that EPYC is affected.
- It does not describe the TEE's design, threat model or security guarantees.
- It does not say the TEE is open source.
- It does not show that retail hardware has shipped or that anyone can activate this firmware today.
What PMF does, and why 20 BIOS inputs matter
The Platform Management Framework is AMD's power and thermal policy layer. Its Linux driver was described at merge time as a centralized framework based on sensor inputs, OS hints, platform state and APU metrics to dynamically manage perf, power and system thermals. Phoronix summarizes the trusted application here as managing power, thermal, and system behavior.
Earlier Phoronix coverage explains the loading mechanism. The PMF driver loads the PMF TA into the AMD ASP's TEE, and the firmware under /lib/firmware/amdtee loads only when the TEE environment is initialized. That fits the new commit's amdtee/ file path.
A bigger shared-memory layout and room for up to 20 custom BIOS inputs suggest laptop makers get more room to tune policy. This is my reading, not something the commit spells out. The commit gives no policy list, and it shows no user-visible controls or performance data.
Practical impact for Windows and Linux users
Nothing needs doing now. No retail systems, BIOS versions or update procedures are tied to this commit, and Phoronix says the Zen 6 products haven't officially launched. Existing machines aren't affected.
Three things are worth watching once Zen 6 laptops arrive:
- Firmware and BIOS updates. PMF behavior depends on the TA firmware and the OEM's BIOS inputs together.
- Security documentation. If AMD does move its security processor to RISC-V, expect it to say so in security briefings or in advisories that mention the TEE.
- Linux enablement. Distributions that ship an up-to-date linux-firmware package will pick up the file automatically. Kernel support for the platform is tracked separately, and Zen 6 PMF changes were reported in Linux 7.3.
The takeaway
This is a small commit with a big question attached. AMD's own firmware says the PMF trusted application for a Zen 6-era platform runs on a RISC-V-based TEE. Whether that is a Zen 6 first or a long-unmentioned detail of recent chips is something only AMD can answer. For now, it's a useful clue to what's inside the next generation of Ryzen security hardware.