Firmware area
AMD Secure Processor and SMU firmware
The CVEs of the AMD Secure Processor (PSP): its boot ROM and boot loader, its Trusted OS and applications, the firmware TPM, and the System Management Unit.
- Also known as
- AMD Platform Security Processor, PSP, ASP, System Management Unit
- Kind
- Firmware
- CVEs
- 132
- Published
- 2018–2026
The AMD Secure Processor, called the Platform Security Processor (PSP) in older records, is the security processor built into AMD’s processors. Its boot ROM loads and checks the boot loader from the SPI flash; the boot loader runs the AGESA boot loader (ABL) and user applications, among them the DRTM service, and a Trusted OS hosts trusted applications such as the firmware TPM (fTPM). The System Management Unit (SMU) and its power management firmware also take requests from the rest of the chip. Most CVEs here are flaws in the system calls and mailboxes through which these parts take requests from x86 code, from a compromised ABL or from a user application on the Secure Processor.
AMD fixes them in the platform initialization (PI) firmware it gives board makers, so a fix arrives as a BIOS update; each bulletin lists the PI version for every product line. The monthly server, client and embedded bulletins below also hold CVEs of SEV (on the AMD SEV page) and of AGESA and SMM (on the AMD AGESA and SMM page); each lists all its CVEs, and AMD’s host driver and software CVEs, which these pages leave out, are not listed. The CVEs of CTS Labs’ 2018 reports came before AMD had a bulletin series and cite AMD’s statement of that March; the Promontory chipset CVEs among them concern the chipset of many socket AM4 and TR4 boards, which AMD’s statement says EPYC, embedded and FP5 mobile platforms do not use. Bulletins AMD-SB-7002, AMD-SB-4011 and AMD-SB-7064 cover flaws of the TCG TPM 2.0 reference code that AMD’s fTPM uses (CVE-2023-1017, CVE-2023-1018, CVE-2025-2884, CVE-2026-6726 and CVE-2026-6727); their records name the reference code, not AMD’s processors, so this page does not list them. The bulletins below link those that the Intel CSME, SPS, TXE and AMT page lists, where Intel’s firmware TPM uses the same code.
CVEs
| CVE | Name | Vendors | Published |
|---|---|---|---|
| CVE-2018-8930 | Hardware Validated Boot bypass (MASTERKEY) (described below) | AMD | 2018-03-22 |
| CVE-2018-8931 | Secure Processor access from x86 (RYZENFALL-1) (described below) | AMD | 2018-03-22 |
| CVE-2018-8932 | Secure Processor access from x86 (RYZENFALL-2 to 4) (described below) | AMD | 2018-03-22 |
| CVE-2018-8933 | Protected memory regions on EPYC (FALLOUT) (described below) | AMD | 2018-03-22 |
| CVE-2018-8934 | Promontory chipset firmware (CHIMERA-FW) (described below) | AMD | 2018-03-22 |
| CVE-2018-8935 | Promontory chipset hardware (CHIMERA-HW) (described below) | AMD | 2018-03-22 |
| CVE-2018-8936 | Secure Processor privilege escalation (described below) | AMD | 2018-03-22 |
| CVE-2020-12926 | fTPM failed-shutdown counting (described below) | AMD | 2020-11-12 |
| CVE-2020-12930 | Secure Processor driver parameters (described below) | AMD | 2022-11-09 |
| CVE-2020-12931 | Secure Processor kernel parameters (described below) | AMD | 2022-11-09 |
| CVE-2020-12944 | BIOS image length check (described below) | AMD | 2021-11-16 |
| CVE-2020-12946 | Discrete TPM command input (described below) | AMD | 2021-11-16 |
| CVE-2020-12951 | Race into ASP SMM operations (described below) | AMD | 2021-11-16 |
| CVE-2020-12961 | Zeroing System Management Network registers (described below) | AMD | 2021-11-16 |
| CVE-2021-26315 | Encrypted firmware integrity in the boot ROM (described below) | AMD | 2021-11-16 |
| CVE-2021-26322 | IV reuse for the platform private key (described below) | AMD | 2021-11-16 |
| CVE-2021-26329 | SMU integer overflow (described below) | AMD | 2021-11-16 |
| CVE-2021-26330 | SMU heap overflow (described below) | AMD | 2021-11-16 |
| CVE-2021-26331 | SMU mailbox entries (described below) | AMD | 2021-11-16 |
| CVE-2021-26335 | Bootloader image header checks (described below) | AMD | 2021-11-16 |
| CVE-2021-26336 | SMU bounds checks (described below) | AMD | 2021-11-16 |
| CVE-2021-26337 | SMU DMA from bad DRAM addresses (described below) | AMD | 2021-11-16 |
| CVE-2021-26338 | SMU performance control tables (described below) | AMD | 2021-11-16 |
| CVE-2021-26343 | ASP BIOS and DRTM commands (described below) | AMD | 2023-01-10 |
| CVE-2021-26344 | Out-of-bounds write in the APCB (described below) | AMD | 2024-08-13 |
| CVE-2021-26345 | APCB token value (described below) | AMD | 2023-11-14 |
| CVE-2021-26346 | L2 directory integer overflow (2023) (described below) | AMD | 2023-01-10 |
| CVE-2021-26347 | L2 directory integer overflow (2022) (described below) | AMD | 2022-05-11 |
| CVE-2021-26350 | SMU message port race (described below) | AMD | 2022-05-11 |
| CVE-2021-26351 | SMU DMA to bad DRAM addresses (described below) | AMD | 2022-05-12 |
| CVE-2021-26352 | SMU PCIe hot plug table (described below) | AMD | 2022-05-10 |
| CVE-2021-26353 | DRTM user application left half set up (described below) | AMD | 2022-05-10 |
| CVE-2021-26354 | Zeroing memory from a compromised ABL (described below) | AMD | 2023-05-09 |
| CVE-2021-26355 | SMU message port registers (described below) | AMD | 2023-01-10 |
| CVE-2021-26356 | SPI ROM changed after it is read (described below) | AMD | 2023-05-09 |
| CVE-2021-26361 | Memory exfiltration from the stage 2 bootloader (described below) | AMD | 2022-05-12 |
| CVE-2021-26362 | Mapping SMN registers from a user application (described below) | AMD | 2022-05-12 |
| CVE-2021-26363 | Moving the ASP's reserved DRAM (described below) | AMD | 2022-05-12 |
| CVE-2021-26364 | SMU mailbox register bounds (described below) | AMD | 2022-05-11 |
| CVE-2021-26365 | Size values in firmware headers (described below) | AMD | 2023-05-09 |
| CVE-2021-26366 | Boot ROM readout (described below) | AMD | 2022-05-12 |
| CVE-2021-26367 | Trusted memory region setup from x86 (described below) | AMD | 2024-08-13 |
| CVE-2021-26368 | Trusted OS process type check (described below) | AMD | 2022-05-12 |
| CVE-2021-26369 | Malformed bootloader system call (described below) | AMD | 2022-05-12 |
| CVE-2021-26370 | Firmware load destination address (described below) | AMD | 2022-05-10 |
| CVE-2021-26371 | SHA256 system call exposes ASP memory (described below) | AMD | 2023-05-09 |
| CVE-2021-26372 | SMU PCIe bounds checks (described below) | AMD | 2022-05-11 |
| CVE-2021-26373 | SMU voltage malfunction (described below) | AMD | 2022-05-11 |
| CVE-2021-26375 | SMU GPIO bounds checks (described below) | AMD | 2022-05-11 |
| CVE-2021-26376 | SMU FeatureConfig (described below) | AMD | 2022-05-11 |
| CVE-2021-26377 | Trusted OS process space overflow (described below) | AMD | 2025-09-06 |
| CVE-2021-26378 | SMU address bounds checks (described below) | AMD | 2022-05-11 |
| CVE-2021-26379 | SMU mailbox corrupts SMRAM (described below) | AMD | 2023-05-09 |
| CVE-2021-26380 | Malformed call from a Trusted OS driver (described below) | AMD | 2026-05-15 |
| CVE-2021-26381 | Trusted OS mapping system call (described below) | AMD | 2026-02-10 |
| CVE-2021-26383 | AMD TEE command bounds (described below) | AMD | 2025-09-05 |
| CVE-2021-26386 | Malformed call to the stage 2 bootloader (described below) | AMD | 2022-05-12 |
| CVE-2021-26387 | ASP kernel DRAM mapping (described below) | AMD | 2024-08-13 |
| CVE-2021-26390 | Bootloader corrupts memory for a user application (described below) | AMD | 2022-05-10 |
| CVE-2021-26392 | LoadModule size check (described below) | AMD | 2022-11-09 |
| CVE-2021-26393 | TEE memory not cleared (described below) | AMD | 2022-11-09 |
| CVE-2021-26397 | Address validation for ABL and user application (described below) | AMD | 2023-05-09 |
| CVE-2021-26398 | SYS_KEY_DERIVE system call (described below) | AMD | 2023-01-10 |
| CVE-2021-26407 | Random IV collisions (described below) | AMD | 2023-01-10 |
| CVE-2021-26410 | ASP kernel reads its own memory as parameters (described below) | AMD | 2026-02-10 |
| CVE-2021-46746 | No stack protection in the ASP Secure OS (described below) | AMD | 2024-08-13 |
| CVE-2021-46747 | Mapping SMN apertures from user space (described below) | AMD | 2026-06-01 |
| CVE-2021-46749 | SMI mailbox checksum read (described below) | AMD | 2023-05-09 |
| CVE-2021-46750 | Graphics mailbox overlaps a TMR (described below) | AMD | 2025-09-06 |
| CVE-2021-46753 | Sensor fusion hub header lengths (described below) | AMD | 2023-05-09 |
| CVE-2021-46754 | Bootloader leaks to the SMU (described below) | AMD | 2023-05-09 |
| CVE-2021-46755 | SysHub mappings left in error paths (described below) | AMD | 2023-05-09 |
| CVE-2021-46756 | SVC_MAP_USER_STACK input (described below) | AMD | 2023-05-09 |
| CVE-2021-46757 | Secure OS kernel memory from a TA (described below) | AMD | 2024-02-13 |
| CVE-2021-46758 | SPI flash addresses in the bootloader (described below) | AMD | 2023-11-14 |
| CVE-2021-46759 | TEE memory to the serial port (described below) | AMD | 2023-05-09 |
| CVE-2021-46760 | Out-of-bounds bootloader system call (described below) | AMD | 2023-05-09 |
| CVE-2021-46762 | SMU SRAM corruption (described below) | AMD | 2023-05-09 |
| CVE-2021-46763 | SMU shared buffer overflow (described below) | AMD | 2023-05-09 |
| CVE-2021-46764 | SMU overwrites ASP memory (described below) | AMD | 2023-05-09 |
| CVE-2021-46765 | ASP reads from a compromised SMM (described below) | AMD | 2023-05-09 |
| CVE-2021-46766 | Keys left in bootloader SRAM (described below) | AMD | 2023-11-14 |
| CVE-2021-46767 | ASP writes from physical access (described below) | AMD | 2023-01-10 |
| CVE-2021-46769 | Arbitrary DMA copies from the bootloader (described below) | AMD | 2023-05-09 |
| CVE-2021-46771 | ASP firmware system call addresses (described below) | AMD | 2022-05-10 |
| CVE-2021-46772 | ABL and SPI ROM structure headers (described below) | AMD | 2024-08-13 |
| CVE-2021-46773 | ABL corrupts ASP memory (described below) | AMD | 2023-05-09 |
| CVE-2021-46774 | SMU DRAM address checks (described below) | AMD | 2023-11-14 |
| CVE-2021-46775 | ABL memory overwrite with physical access (described below) | AMD | 2023-05-09 |
| CVE-2021-46779 | SVC_ECC_PRIMITIVE system call (described below) | AMD | 2023-01-10 |
| CVE-2021-46791 | SMM binary corrupts DRTM memory (described below) | AMD | 2023-01-10 |
| CVE-2021-46792 | BIOS2PSP race on S3 resume (described below) | AMD | 2023-05-09 |
| CVE-2021-46794 | SMI mailbox checksum read (second CVE) (described below) | AMD | 2023-05-09 |
| CVE-2021-46795 | TEE OS reads out of bounds (described below) | AMD | 2023-01-10 |
| CVE-2022-23815 | APCB out-of-bounds write (described below) | AMD | 2024-08-13 |
| CVE-2022-23817 | Secure OS kernel memory from a TA (described below) | AMD | 2024-08-13 |
| CVE-2023-20507 | ASP integer overflow (described below) | AMD | 2025-02-11 |
| CVE-2023-20508 | ASP out-of-bounds write (described below) | AMD | 2025-02-11 |
| CVE-2023-20515 | fTPM driver in the Trusted OS (described below) | AMD | 2025-02-11 |
| CVE-2023-20518 | Master Encryption Key left in memory (described below) | AMD | 2024-08-13 |
| CVE-2023-20520 | Bootloader return address (described below) | AMD | 2023-05-09 |
| CVE-2023-20521 | SPI ROM records changed after verification (described below) | AMD | 2023-11-14 |
| CVE-2023-20522 | ASP input from a malicious BIOS (described below) | AMD | 2023-01-10 |
| CVE-2023-20523 | ASP buffer overflow with physical access (described below) | AMD | 2023-01-10 |
| CVE-2023-20524 | Malformed commands to another socket's ASP (described below) | AMD | 2023-05-09 |
| CVE-2023-20525 | Bootloader reads beyond a mapped register (described below) | AMD | 2023-01-10 |
| CVE-2023-20526 | ASP memory exposed with physical access (described below) | AMD | 2023-11-14 |
| CVE-2023-20527 | Bootloader out-of-bounds read (described below) | AMD | 2023-01-10 |
| CVE-2023-20528 | SMU memory over I2C (described below) | AMD | 2023-01-10 |
| CVE-2023-20529 | SMU from/to addresses (described below) | AMD | 2023-01-10 |
| CVE-2023-20530 | SMU BIOS mailbox messages (described below) | AMD | 2023-01-10 |
| CVE-2023-20531 | SMU SRAM from/to addresses (described below) | AMD | 2023-01-10 |
| CVE-2023-20532 | SMU resource locking (described below) | AMD | 2023-01-10 |
| CVE-2023-20533 | SMU DRAM addresses (2023) (described below) | AMD | 2023-11-14 |
| CVE-2023-20540 | HMAC timing in the ASP (described below) | AMD | 2026-06-26 |
| CVE-2023-20572 | HMAC timing in the ASP (client) (described below) | AMD | 2026-06-26 |
| CVE-2023-20589 | Voltage fault injection on fTPM secure boot (faulTPM) | AMD | 2023-08-08 |
| CVE-2023-20591 | IOMMU not reset at a DRTM event (described below) | AMD | 2024-08-13 |
| CVE-2023-20599 | Crypto Co-Processor registers from x86 | AMD | 2025-06-10 |
| CVE-2023-31316 | VCN firmware flow after power save (described below) | AMD | 2026-05-15 |
| CVE-2023-31325 | PSP reserved DRAM tampering (described below) | AMD | 2025-09-06 |
| CVE-2023-31326 | Leftover TEE driver data (described below) | AMD | 2025-09-06 |
| CVE-2023-31330 | ASP out-of-bounds read from a bootloader (described below) | AMD | 2025-09-06 |
| CVE-2023-31331 | DRTM driver initialized twice (described below) | AMD | 2025-02-11 |
| CVE-2024-21970 | Power management firmware array index (described below) | AMD | 2025-09-06 |
| CVE-2024-21981 | ASP key usage control (described below) | AMD | 2024-08-13 |
| CVE-2025-0044 | Power management firmware read (described below) | AMD | 2026-05-15 |
| CVE-2025-29949 | Bootloader legacy recovery mode (described below) | AMD | 2026-02-10 |
| CVE-2025-29951 | Bootloader buffer overflow (described below) | AMD | 2026-02-10 |
| CVE-2025-48515 | Bootloader input on SPI ROM upgrade (described below) | AMD | 2026-02-10 |
| CVE-2025-48516 | DDR5 PMIC left unprotected (described below) | AMD | 2026-05-15 |
| CVE-2025-54509 | Non-coherent Secure Processor memory access | AMD | 2026-06-09 |
CVEs without a page of their own
The sources give these CVEs too few facts of their own (affected processors, a mitigation, a check) for a page; this is what they say.
CVE-2018-8930: Hardware Validated Boot bypass (MASTERKEY)
Firmware written to flash could pass the Secure Processor's validated boot checks, so altered firmware ran at every boot (CTS Labs' MASTERKEY). Source. CVE record (2018-03-22).
CVE-2018-8931: Secure Processor access from x86 (RYZENFALL-1)
Weak access control between x86 and the Secure Processor on Ryzen let an administrator attack the Secure Processor (CTS Labs' RYZENFALL-1). Source. CVE record (2018-03-22).
CVE-2018-8932: Secure Processor access from x86 (RYZENFALL-2 to 4)
More flaws in the interface between x86 and the Secure Processor of Ryzen chips (CTS Labs' RYZENFALL-2, -3 and -4). Source. CVE record (2018-03-22).
CVE-2018-8933: Protected memory regions on EPYC (FALLOUT)
Weak access control to protected memory regions on EPYC let an administrator reach memory the Secure Processor guards (CTS Labs' FALLOUT). Source. CVE record (2018-03-22).
CVE-2018-8934: Promontory chipset firmware (CHIMERA-FW)
CTS Labs reported a backdoor in the firmware of the Promontory chipset that many AM4 and TR4 boards use (CHIMERA-FW). Source. CVE record (2018-03-22).
CVE-2018-8935: Promontory chipset hardware (CHIMERA-HW)
CTS Labs reported a backdoor in the Promontory chipset itself; AMD says EPYC, embedded and FP5 mobile platforms do not use that chipset. Source. CVE record (2018-03-22).
CVE-2018-8936: Secure Processor privilege escalation
A flaw in the Platform Security Processor let an attacker raise privileges on it, on EPYC and Ryzen (one of the CTS Labs reports). Source. CVE record (2018-03-22).
CVE-2020-12926: fTPM failed-shutdown counting
The TPM reference code that AMD's firmware TPM uses could miscount failed shutdowns, exposing TPM keys to an attacker who can cut the power often. Source. CVE record (2020-11-12).
CVE-2020-12930: Secure Processor driver parameters
Secure Processor drivers did not handle their parameters properly, which let a privileged attacker raise privileges and harm integrity. AMD-SB-1029. Source. CVE record (2022-11-09).
CVE-2020-12931: Secure Processor kernel parameters
The Secure Processor kernel did not handle parameters properly, which let a privileged attacker raise privileges and harm integrity. AMD-SB-1029. Source. CVE record (2022-11-09).
CVE-2020-12944: BIOS image length check
The Secure Processor firmware did not check the length of the BIOS image well enough, which could lead to code execution. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2020-12946: Discrete TPM command input
The Secure Processor firmware did not validate input of discrete TPM commands, which could harm integrity or stop the system. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2020-12951: Race into ASP SMM operations
A race in the Secure Processor firmware let less privileged x86 code carry out operations reserved to SMM. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2020-12961: Zeroing System Management Network registers
An attacker could make the Platform Security Processor zero privileged registers on the System Management Network and so bypass SPI ROM protections. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26315: Encrypted firmware integrity in the boot ROM
The boot ROM did not fully check the integrity of firmware it decrypted, so a crafted encrypted image could run code on the Secure Processor. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26322: IV reuse for the platform private key
The persistent platform private key might be encrypted without a random IV, which opens a two-time pad attack on it. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26329: SMU integer overflow
An invalid length could overflow an integer in the System Management Unit and use up its resources. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26330: SMU heap overflow
A heap overflow in the System Management Unit firmware could use up its resources. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26331: SMU mailbox entries
A malicious user could manipulate mailbox entries of the System Management Unit and run code of their own. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26335: Bootloader image header checks
The Secure Processor boot loader used values from an image header before checking its signature, which could let an attacker run code. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26336: SMU bounds checks
Missing bounds checks could make the System Management Unit hang and stop serving the other parts of the chip. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26337: SMU DMA from bad DRAM addresses
The System Management Unit did not validate DRAM addresses, and a DMA read from a bad one could stop it. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26338: SMU performance control tables
Weak access control let an attacker override the System Management Unit's performance control tables in DRAM. AMD-SB-1021. Source. CVE record (2021-11-16).
CVE-2021-26343: ASP BIOS and DRTM commands
Malicious supervisor x86 code could make Secure Processor BIOS and DRTM commands disclose sensitive memory. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-26344: Out-of-bounds write in the APCB
An attacker able to modify and sign the BIOS image could write out of bounds while the APCB is processed and run code. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2021-26345: APCB token value
A tampered APCB token value could force an out-of-bounds read and stop the system. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2021-26346: L2 directory integer overflow (2023)
An integer the boot loader did not validate could overflow in the L2 directory table in SPI flash and stop boot; Ryzen 5000. AMD-SB-1031. Source. CVE record (2023-01-10).
CVE-2021-26347: L2 directory integer overflow (2022)
AMD's record for this boot loader overflow in the SPI flash L2 directory table repeats CVE-2021-26346's text; it was published earlier. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26350: SMU message port race
A race in the System Management Unit let a caller learn and change the address of a message port register and stop the unit. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26351: SMU DMA to bad DRAM addresses
Unvalidated DRAM addresses could make the System Management Unit read or write through DMA where it should not, causing a denial of service. AMD-SB-1021. Source. CVE record (2022-05-12).
CVE-2021-26352: SMU PCIe hot plug table
Missing bounds checks on the System Management Unit's PCIe hot plug table allowed accesses outside it and a denial of service. AMD-SB-1021. Source. CVE record (2022-05-10).
CVE-2021-26353: DRTM user application left half set up
Unvalidated SMM input could leave the DRTM user application of the Secure Processor partly initialized, harming memory integrity. AMD-SB-1021. Source. CVE record (2022-05-10).
CVE-2021-26354: Zeroing memory from a compromised ABL
A compromised AGESA boot loader could make a Secure Processor system call set arbitrary memory to zero. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-26355: SMU message port registers
Missing fencing and checks let accesses reach invalid System Management Unit message port registers and stop the unit. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-26356: SPI ROM changed after it is read
A race in the boot loader let an attacker change SPI ROM data after it was read into memory, corrupting S3 data and leaking information. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-26361: Memory exfiltration from the stage 2 bootloader
A malicious user application or ABL could read arbitrary memory of the Secure Processor's stage 2 boot loader. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26362: Mapping SMN registers from a user application
A malformed system call from a user application or ABL could map sensitive System Management Network registers. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26363: Moving the ASP's reserved DRAM
A malicious user application or ABL could move the Secure Processor's reserved DRAM outside the fenced area and expose data. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26364: SMU mailbox register bounds
Missing bounds checks on an SMU mailbox register allowed reads outside SRAM and an exception that stops the unit. AMD-SB-1028. Source. CVE record (2022-05-11).
CVE-2021-26365: Size values in firmware headers
Size fields in firmware headers could cause out-of-bounds reads during signature checks, stopping the system or leaking a little memory. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-26366: Boot ROM readout
An attacker with privileges gained elsewhere could read the contents of the Secure Processor boot ROM. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26367: Trusted memory region setup from x86
x86 code could set a trusted memory region (TMR) to an arbitrary address range, harming integrity and availability. AMD-SB-4004. Source. CVE record (2024-08-13).
CVE-2021-26368: Trusted OS process type check
The Trusted OS did not check process types well, so a lesser process could unmap memory of a more privileged one. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26369: Malformed bootloader system call
A malicious user application or ABL could send a malformed system call that made the boot loader access memory out of bounds. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26370: Firmware load destination address
Two firmware-loading system calls did not validate their destination, so boot loader memory could be overwritten with SPI ROM data. AMD-SB-1021. Source. CVE record (2022-05-10).
CVE-2021-26371: SHA256 system call exposes ASP memory
A malicious ABL or user application could use the boot loader's SHA256 system call to expose Secure Processor memory. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-26372: SMU PCIe bounds checks
Missing PCIe-related bounds checks in the System Management Unit allowed accesses to invalid addresses and a denial of service. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26373: SMU voltage malfunction
Missing bounds checks in the System Management Unit could cause a voltage malfunction and a denial of service. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26375: SMU GPIO bounds checks
Missing GPIO bounds checks in the System Management Unit allowed accesses outside the intended space and a denial of service. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26376: SMU FeatureConfig
Missing checks in the SMU's FeatureConfig let disabled features be turned back on. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26377: Trusted OS process space overflow
Missing checks when the Trusted OS allocates process space let a malicious process overflow an integer and stop it. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2021-26378: SMU address bounds checks
Missing bounds checks in the System Management Unit allowed accesses to invalid address space and a denial of service. AMD-SB-1027. Source. CVE record (2022-05-11).
CVE-2021-26379: SMU mailbox corrupts SMRAM
Unvalidated mailbox data could make the System Management Unit corrupt SMRAM, raising privileges. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-26380: Malformed call from a Trusted OS driver
A compromised Trusted OS driver could issue a call that reached memory outside its range. AMD-SB-4017. Source. CVE record (2026-05-15).
CVE-2021-26381: Trusted OS mapping system call
A malicious driver could make the Trusted OS map or unmap a large number of pages and corrupt its kernel memory. AMD-SB-4013. Source. CVE record (2026-02-10).
CVE-2021-26383: AMD TEE command bounds
A compromised user process could send the AMD TEE a command with malformed arguments that accessed memory out of bounds. AMD-SB-4012. Source. CVE record (2025-09-05).
CVE-2021-26386: Malformed call to the stage 2 bootloader
A malicious user application or ABL could corrupt memory of the stage 2 boot loader through a system call and run code. AMD-SB-1027. Source. CVE record (2022-05-12).
CVE-2021-26387: ASP kernel DRAM mapping
An attacker with AMD signing keys and BIOS setup access could make the Secure Processor kernel map DRAM in protected areas. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2021-26390: Bootloader corrupts memory for a user application
A malicious user application or ABL could make the boot loader corrupt arbitrary memory. AMD-SB-1021. Source. CVE record (2022-05-10).
CVE-2021-26392: LoadModule size check
A missing size check in LoadModule allowed an out-of-bounds write when a malicious trusted application is loaded. AMD-SB-1029. Source. CVE record (2022-11-09).
CVE-2021-26393: TEE memory not cleared
The Secure Processor TEE did not clean memory, so an attacker able to sign a trusted application could fill its memory with chosen data. AMD-SB-1029. Source. CVE record (2022-11-09).
CVE-2021-26397: Address validation for ABL and user application
Missing address checks let a compromised ABL and user application corrupt sensitive memory of the Secure Processor. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-26398: SYS_KEY_DERIVE system call
Missing checks in the SYS_KEY_DERIVE system call let a malicious user application or ABL corrupt Secure Processor OS memory. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-26407: Random IV collisions
Randomly drawn initialization vectors could repeat under the same key and disclose data; second generation EPYC. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-26410: ASP kernel reads its own memory as parameters
Bad syscall input could make the Secure Processor kernel read parameters from its own memory, letting an attacker infer its contents. AMD-SB-5007. Source. CVE record (2026-02-10).
CVE-2021-46746: No stack protection in the ASP Secure OS
The Secure OS lacked stack protection, so an attacker with AMD signing keys could overrun a stack buffer and stop it. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2021-46747: Mapping SMN apertures from user space
Coarse access control let an untrusted user space application on the Secure Processor map sensitive SMN apertures. AMD-SB-4017. Source. CVE record (2026-06-01).
CVE-2021-46749: SMI mailbox checksum read
Missing bounds checks in the SMI mailbox checksum let the Secure Processor read out of bounds and stop. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46750: Graphics mailbox overlaps a TMR
Unvalidated messages to the graphics mailbox could overlap a trusted memory region set up by the boot loader. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2021-46753: Sensor fusion hub header lengths
A malicious user application or ABL could use bad header lengths to map the sensor fusion hub region and overwrite data. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46754: Bootloader leaks to the SMU
A compromised user application or ABL could make the boot loader expose sensitive data to the System Management Unit. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46755: SysHub mappings left in error paths
Error paths of the boot loader left SysHub mappings in place, so a malicious boot loader could exhaust them. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46756: SVC_MAP_USER_STACK input
Missing checks in the boot loader's SVC_MAP_USER_STACK let a malicious user application or ABL send bad system calls. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46757: Secure OS kernel memory from a TA
A malicious trusted application could read and write the Secure OS kernel's address space, raising privileges. AMD-SB-5001. Source. CVE record (2024-02-13).
CVE-2021-46758: SPI flash addresses in the bootloader
The boot loader did not check SPI flash addresses, so data mapped beyond the flash could be read. AMD-SB-4002. Source. CVE record (2023-11-14).
CVE-2021-46759: TEE memory to the serial port
With physical access and a user application under the boot loader, an attacker could dump boot loader memory to a serial port. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46760: Out-of-bounds bootloader system call
A malformed system call from a user application or ABL made the boot loader access memory out of bounds; Threadripper 3000. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46762: SMU SRAM corruption
Missing input checks let an attacker corrupt the System Management Unit's SRAM. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46763: SMU shared buffer overflow
Missing input checks let a privileged attacker write past a shared memory buffer of the System Management Unit. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46764: SMU overwrites ASP memory
Unvalidated DRAM addresses let the System Management Unit be used to overwrite sensitive memory in the Secure Processor. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46765: ASP reads from a compromised SMM
An attacker who controls SMM could make the Secure Processor read out of bounds and stop. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46766: Keys left in bootloader SRAM
The boot loader did not clear secret keys from Secure Processor SRAM, where a privileged attacker could read them. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2021-46767: ASP writes from physical access
Missing input checks let an attacker with physical access write memory without authorization through the Secure Processor. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-46769: Arbitrary DMA copies from the bootloader
Missing syscall input checks let a privileged attacker make the boot loader do arbitrary DMA copies and run code. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46771: ASP firmware system call addresses
Addresses in a Secure Processor firmware system call were not validated, so a compromised user application could run code. AMD-SB-1021. Source. CVE record (2022-05-10).
CVE-2021-46772: ABL and SPI ROM structure headers
Tampered structure headers in SPI ROM could make the AGESA boot loader read and write out of bounds. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2021-46773: ABL corrupts ASP memory
Missing input checks in the AGESA boot loader let a privileged attacker corrupt Secure Processor memory. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46774: SMU DRAM address checks
Unvalidated DRAM addresses in the System Management Unit allowed reads and writes at invalid addresses. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2021-46775: ABL memory overwrite with physical access
Missing input checks in the AGESA boot loader let an attacker with physical access overwrite arbitrary memory. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2021-46779: SVC_ECC_PRIMITIVE system call
Missing checks in the SVC_ECC_PRIMITIVE system call let a malicious user application or ABL corrupt Secure Processor OS memory. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-46791: SMM binary corrupts DRTM memory
A crafted SMM binary could corrupt memory of the DRTM user application while it is parsed. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2021-46792: BIOS2PSP race on S3 resume
A malicious BIOS could race the BIOS2PSP command so that the boot loader read SRAM out of bounds on S3 resume. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46794: SMI mailbox checksum read (second CVE)
AMD gave a second CVE, with the same description, to an out-of-bounds read in the SMI mailbox checksum that stops the Secure Processor. AMD-SB-4001. Source. CVE record (2023-05-09).
CVE-2021-46795: TEE OS reads out of bounds
A compromised BIOS could race the TEE OS into reading memory out of bounds. AMD-SB-1031. Source. CVE record (2023-01-10).
CVE-2022-23815: APCB out-of-bounds write
Missing bounds checks let an attacker write out of bounds and corrupt an APCB entry, which could lead to code execution. AMD-SB-4004. Source. CVE record (2024-08-13).
CVE-2022-23817: Secure OS kernel memory from a TA
A malicious trusted application could read and write the Secure OS kernel's address space. AMD-SB-4004. Source. CVE record (2024-08-13).
CVE-2023-20507: ASP integer overflow
An integer overflow in the Secure Processor let a privileged attacker write out of bounds. AMD-SB-4008. Source. CVE record (2025-02-11).
CVE-2023-20508: ASP out-of-bounds write
Weak access control in the Secure Processor let a privileged attacker write to memory outside its control. AMD-SB-6008. Source. CVE record (2025-02-11).
CVE-2023-20515: fTPM driver in the Trusted OS
Weak access control in the Trusted OS's fTPM driver let a privileged attacker corrupt memory. AMD-SB-4008. Source. CVE record (2025-02-11).
CVE-2023-20518: Master Encryption Key left in memory
Incomplete cleanup could expose the Master Encryption Key to an attacker with BIOS setup access and a way to read memory. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2023-20520: Bootloader return address
Weak access control in the boot loader let an attacker corrupt a return address and overrun a stack buffer. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2023-20521: SPI ROM records changed after verification
A race in the boot loader let an attacker with physical access change SPI ROM records after they were verified. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2023-20522: ASP input from a malicious BIOS
Missing input checks let a malicious BIOS stop the Secure Processor. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20523: ASP buffer overflow with physical access
A race in the Secure Processor let a physical attacker write past a buffer. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20524: Malformed commands to another socket's ASP
A compromised Secure Processor could send malformed commands to the one on the other socket and write out of bounds. AMD-SB-3001. Source. CVE record (2023-05-09).
CVE-2023-20525: Bootloader reads beyond a mapped register
Missing syscall checks let a privileged attacker make the boot loader read beyond a mapped register. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20526: ASP memory exposed with physical access
Missing input checks in the boot loader let a privileged attacker with physical access expose Secure Processor memory. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2023-20527: Bootloader out-of-bounds read
Missing syscall checks let a privileged attacker make the boot loader read out of bounds. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20528: SMU memory over I2C
Missing input checks let a physical attacker read the System Management Unit's memory over the I2C bus. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20529: SMU from/to addresses
Missing bounds checks let an attacker set the System Management Unit's from/to addresses to invalid values. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20530: SMU BIOS mailbox messages
Unvalidated BIOS mailbox messages made the System Management Unit read out of bounds. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20531: SMU SRAM from/to addresses
Missing bounds checks let an attacker set the SRAM addresses the System Management Unit copies from and to. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20532: SMU resource locking
Missing input checks let an attacker lock System Management Unit resources and cause a denial of service. AMD-SB-1032. Source. CVE record (2023-01-10).
CVE-2023-20533: SMU DRAM addresses (2023)
Unvalidated DRAM addresses in the System Management Unit allowed reads and writes at invalid addresses. AMD-SB-3002. Source. CVE record (2023-11-14).
CVE-2023-20540: HMAC timing in the ASP
A timing difference in the Secure Processor let a privileged attacker brute-force an HMAC and pass chosen messages. AMD-SB-4012. Source. CVE record (2026-06-26).
CVE-2023-20572: HMAC timing in the ASP (client)
The same kind of timing difference in the Secure Processor's HMAC check, listed for more client processors. AMD-SB-4012. Source. CVE record (2026-06-26).
CVE-2023-20591: IOMMU not reset at a DRTM event
The IOMMU was not set up again during a DRTM launch, so an untrusted configuration could survive and expose hypervisor memory. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2023-31316: VCN firmware flow after power save
State the Secure Processor saved across a power save could be changed to redirect the Video Core Next firmware. AMD-SB-4017. Source. CVE record (2026-05-15).
CVE-2023-31325: PSP reserved DRAM tampering
Poor isolation of shared resources let a privileged attacker change the Secure Processor's reserved DRAM. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2023-31326: Leftover TEE driver data
An uninitialized variable in the Secure Processor let an attacker read data a TEE driver left behind. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2023-31330: ASP out-of-bounds read from a bootloader
A privileged attacker with a malicious boot loader could make the Secure Processor read sensitive memory. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2023-31331: DRTM driver initialized twice
Weak access control in the DRTM firmware let a privileged attacker initialize drivers more than once and corrupt the stack. AMD-SB-4008. Source. CVE record (2025-02-11).
CVE-2024-21970: Power management firmware array index
An unchecked array index in the power management firmware let a privileged attacker corrupt AGESA memory. AMD-SB-4012. Source. CVE record (2025-09-06).
CVE-2024-21981: ASP key usage control
An attacker already running code in the Secure Processor could extract its cryptographic keys. AMD-SB-3003. Source. CVE record (2024-08-13).
CVE-2025-0044: Power management firmware read
An out-of-bounds read in the power management firmware could leak some data or stop it. AMD-SB-6027. Source. CVE record (2026-05-15).
CVE-2025-29949: Bootloader legacy recovery mode
In legacy recovery mode only, bad input to the boot loader let an attacker write out of bounds into secure DRAM. AMD-SB-4013. Source. CVE record (2026-02-10).
CVE-2025-29951: Bootloader buffer overflow
A buffer overflow in the Secure Processor boot loader could let an attacker overwrite memory and run code. AMD-SB-4013. Source. CVE record (2026-02-10).
CVE-2025-48515: Bootloader input on SPI ROM upgrade
An attacker able to upgrade the SPI ROM could pass the boot loader input that overwrote its memory. AMD-SB-4013. Source. CVE record (2026-02-10).
CVE-2025-48516: DDR5 PMIC left unprotected
The AGESA boot loader left the DDR5 module's PMIC interface open, so local code could damage the module for good. AMD-SB-4017. Source. CVE record (2026-05-15).
Advisories
AMD-SB-7064: Trusted Platform Module (TPM) Reference Code Errata
2026-08-11. CVE-2026-6726, CVE-2026-6727
The CVEs are flaws of the TCG TPM 2.0 reference code that AMD's fTPM uses, not of AMD's processors; this page does not list them, and the Intel CSME, SPS, TXE and AMT page does.
AMD-SB-3039: ASP non-Coherent Memory Access
2026-06-09. CVE-2025-54509
AMD-SB-6027: AMD Graphics Vulnerabilities - May 2026
2026-05-12. CVE-2021-26380, CVE-2021-46747, CVE-2022-23817, CVE-2022-23826, CVE-2023-31316, CVE-2025-0040, CVE-2025-0044
AMD-SB-4017: AMD Athlon, AMD Ryzen, and AMD Ryzen Embedded Series Processor Vulnerabilities - May 2026
2026-05-12. CVE-2021-26380, CVE-2021-46747, CVE-2022-23826, CVE-2023-31316, CVE-2024-36315, CVE-2024-36343, CVE-2024-36345, CVE-2025-0040, CVE-2025-48516, CVE-2026-0438
AMD-SB-3045: MilanLaunchy Firmware Loader
2026-05-12. CVE-2021-26315, CVE-2024-21944, CVE-2024-21981
AMD-SB-4013: AMD Athlon and AMD Ryzen Processor Vulnerabilities - February 2026
2026-02-10. CVE-2021-26381, CVE-2021-26410, CVE-2023-20540, CVE-2024-21953, CVE-2024-21961, CVE-2024-36310, CVE-2024-36311, CVE-2024-36355, CVE-2025-0012, CVE-2025-0029, CVE-2025-0031, CVE-2025-29939, CVE-2025-29946, CVE-2025-29948, CVE-2025-29949, CVE-2025-29950, CVE-2025-29951, CVE-2025-29952, CVE-2025-48509, CVE-2025-48514, CVE-2025-48515, CVE-2025-48517, CVE-2025-52533, CVE-2025-52534, CVE-2025-52536, CVE-2025-54514
AMD-SB-7044: Physical Attacks Leading to Bypass of ASP Boot ROM Secure Boot
2025-08-12.
AMD-SB-5007: AMD Embedded Vulnerabilities - August 2025
2025-08-12. CVE-2021-26377, CVE-2021-26383, CVE-2021-26410, CVE-2021-46750, CVE-2021-46757, CVE-2023-20540, CVE-2023-20572, CVE-2023-31326, CVE-2023-31351, CVE-2024-21947, CVE-2024-21970, CVE-2024-21977, CVE-2024-36331, CVE-2024-36354, CVE-2025-0032
AMD-SB-4012: AMD Client Vulnerabilities - August 2025
2025-08-12. CVE-2021-26377, CVE-2021-26383, CVE-2021-46750, CVE-2021-46757, CVE-2023-20540, CVE-2023-20572, CVE-2023-31325, CVE-2023-31326, CVE-2023-31330, CVE-2024-21947, CVE-2024-21970, CVE-2024-21977, CVE-2024-36326, CVE-2024-36354, CVE-2025-0032
AMD-SB-4011: TPM Reference Implementation
2025-06-10. CVE-2025-2884
The CVE is a flaw of the TCG TPM 2.0 reference code that AMD's fTPM uses, not of AMD's processors; this page does not list it, and the Intel CSME, SPS, TXE and AMT page does.
AMD-SB-7039: Unauthorized Access to AMD Secure Processor's Crypto-Co-Processor
2025-06-10. CVE-2023-20599
AMD-SB-6008: AMD Graphics Driver Vulnerabilities - February 2025
2025-02-11. CVE-2023-20508
AMD-SB-5004: AMD Embedded Processors Vulnerabilities - February 2025
2025-02-11. CVE-2023-20507, CVE-2023-20515, CVE-2023-20581, CVE-2023-20582, CVE-2023-31331, CVE-2023-31342, CVE-2023-31343, CVE-2023-31345, CVE-2023-31352, CVE-2023-31356
AMD-SB-4008: AMD Client Processor Vulnerabilities - February 2025
2025-02-11. CVE-2023-20507, CVE-2023-20515, CVE-2023-31331, CVE-2023-31342, CVE-2023-31343, CVE-2023-31345
AMD-SB-5002: AMD Embedded Processors Vulnerabilities - Aug 2024
2024-08-13. CVE-2021-26344, CVE-2021-26367, CVE-2021-26387, CVE-2021-46746, CVE-2021-46772, CVE-2022-23815, CVE-2022-23817, CVE-2023-20518, CVE-2023-20578, CVE-2023-20591, CVE-2024-21981
AMD-SB-4004: Client Vulnerabilities - Aug 2024
2024-08-13. CVE-2021-26344, CVE-2021-26367, CVE-2021-26387, CVE-2021-46746, CVE-2021-46772, CVE-2022-23815, CVE-2022-23817, CVE-2023-20518, CVE-2023-20578, CVE-2024-21981
AMD-SB-3003: AMD Server Vulnerabilities - August 2024
2024-08-13. CVE-2021-26344, CVE-2021-26387, CVE-2021-46746, CVE-2021-46772, CVE-2023-20518, CVE-2023-20578, CVE-2023-20584, CVE-2023-20591, CVE-2023-31356, CVE-2024-21981
AMD-SB-5001: AMD Embedded Processors Vulnerabilities - February 2024
2024-02-13. CVE-2020-12930, CVE-2020-12931, CVE-2021-26345, CVE-2021-26392, CVE-2021-26393, CVE-2021-46754, CVE-2021-46757, CVE-2021-46762, CVE-2021-46766, CVE-2021-46774, CVE-2022-23820, CVE-2022-23821, CVE-2022-23830, CVE-2023-20521, CVE-2023-20526, CVE-2023-20533, CVE-2023-20563, CVE-2023-20565, CVE-2023-20566, CVE-2023-20571
AMD-SB-4002: AMD Client Vulnerabilities - November 2023
2023-11-14. CVE-2021-46758, CVE-2021-46766, CVE-2021-46774, CVE-2022-23820, CVE-2022-23821, CVE-2023-20521, CVE-2023-20526, CVE-2023-20533, CVE-2023-20563, CVE-2023-20565, CVE-2023-20571
AMD-SB-3002: AMD Server Vulnerabilities - Nov 2023
2023-11-14. CVE-2021-26345, CVE-2021-46766, CVE-2021-46774, CVE-2022-23820, CVE-2022-23830, CVE-2023-20519, CVE-2023-20521, CVE-2023-20526, CVE-2023-20533, CVE-2023-20566
AMD-SB-4005: fTPM Voltage Fault Injection
2023-08-08. CVE-2023-20589
AMD-SB-7002: TPM Out of Bounds Access
2023-04-11. CVE-2023-1017, CVE-2023-1018
The CVEs are flaws of the TCG TPM 2.0 reference code that AMD's fTPM uses, not of AMD's processors; this page does not list them, nor does any other.
AMD-SB-4001: Client Vulnerabilities - May 2023
2023-05-09. CVE-2020-12930, CVE-2020-12931, CVE-2021-26354, CVE-2021-26356, CVE-2021-26365, CVE-2021-26371, CVE-2021-26392, CVE-2021-26393, CVE-2021-26406, CVE-2021-46749, CVE-2021-46753, CVE-2021-46754, CVE-2021-46755, CVE-2021-46756, CVE-2021-46759, CVE-2021-46760, CVE-2021-46765, CVE-2021-46773, CVE-2021-46792, CVE-2021-46794
AMD-SB-3001: AMD Server Vulnerabilities - May 2023
2023-05-09. CVE-2021-26354, CVE-2021-26356, CVE-2021-26371, CVE-2021-26379, CVE-2021-26397, CVE-2021-26406, CVE-2021-46755, CVE-2021-46756, CVE-2021-46762, CVE-2021-46763, CVE-2021-46764, CVE-2021-46769, CVE-2021-46775, CVE-2022-23818, CVE-2023-20520, CVE-2023-20524
AMD-SB-1032: AMD Server Vulnerabilities - January 2023
2023-01-10. CVE-2021-26316, CVE-2021-26328, CVE-2021-26343, CVE-2021-26353, CVE-2021-26355, CVE-2021-26396, CVE-2021-26398, CVE-2021-26402, CVE-2021-26403, CVE-2021-26404, CVE-2021-26407, CVE-2021-26409, CVE-2021-39298, CVE-2021-46767, CVE-2021-46768, CVE-2021-46779, CVE-2021-46791, CVE-2022-23813, CVE-2022-23814, CVE-2023-20522, CVE-2023-20523, CVE-2023-20525, CVE-2023-20527, CVE-2023-20528, CVE-2023-20529, CVE-2023-20530, CVE-2023-20531, CVE-2023-20532
AMD-SB-1031: AMD Client Vulnerabilities - January 2023
2023-01-10. CVE-2021-26316, CVE-2021-26346, CVE-2021-46795
AMD-SB-1029: AMD Graphics Driver Vulnerabilities - November 2022
2022-11-08. CVE-2020-12930, CVE-2020-12931, CVE-2021-26392, CVE-2021-26393
AMD-SB-1028: AMD Server Vulnerabilities - May 2022
2022-05-10. CVE-2021-26312, CVE-2021-26339, CVE-2021-26342, CVE-2021-26347, CVE-2021-26348, CVE-2021-26349, CVE-2021-26350, CVE-2021-26364, CVE-2021-26372, CVE-2021-26373, CVE-2021-26375, CVE-2021-26376, CVE-2021-26378, CVE-2021-26388
AMD-SB-1027: AMD Client Vulnerabilities - May 2022
2022-05-10. CVE-2020-12944, CVE-2020-12946, CVE-2020-12951, CVE-2021-26312, CVE-2021-26317, CVE-2021-26335, CVE-2021-26336, CVE-2021-26337, CVE-2021-26339, CVE-2021-26347, CVE-2021-26348, CVE-2021-26349, CVE-2021-26350, CVE-2021-26351, CVE-2021-26352, CVE-2021-26353, CVE-2021-26361, CVE-2021-26362, CVE-2021-26363, CVE-2021-26366, CVE-2021-26368, CVE-2021-26369, CVE-2021-26370, CVE-2021-26372, CVE-2021-26373, CVE-2021-26375, CVE-2021-26376, CVE-2021-26378, CVE-2021-26382, CVE-2021-26384, CVE-2021-26386, CVE-2021-26388, CVE-2021-26390, CVE-2021-39298, CVE-2021-46771, CVE-2023-20558, CVE-2023-20559
AMD-SB-1021: AMD Server Vulnerabilities - November 2021
2021-11-08. CVE-2020-12944, CVE-2020-12946, CVE-2020-12951, CVE-2020-12954, CVE-2020-12961, CVE-2020-12988, CVE-2021-26312, CVE-2021-26315, CVE-2021-26320, CVE-2021-26321, CVE-2021-26322, CVE-2021-26323, CVE-2021-26324, CVE-2021-26325, CVE-2021-26326, CVE-2021-26327, CVE-2021-26329, CVE-2021-26330, CVE-2021-26331, CVE-2021-26332, CVE-2021-26335, CVE-2021-26336, CVE-2021-26337, CVE-2021-26338, CVE-2021-26351, CVE-2021-26352, CVE-2021-26353, CVE-2021-26370, CVE-2021-26390, CVE-2021-26408, CVE-2021-46771
Sources
- AMD: Initial AMD Technical Assessment of CTS Labs Research (2018-03-21)
- AMD Product Security: bulletins archive, 2020
- AMD-SB-7064: Trusted Platform Module (TPM) Reference Code Errata
- AMD-SB-3039: ASP non-Coherent Memory Access
- AMD-SB-6027: AMD Graphics Vulnerabilities - May 2026
- AMD-SB-4017: AMD Athlon, AMD Ryzen, and AMD Ryzen Embedded Series Processor Vulnerabilities - May 2026
- AMD-SB-3045: MilanLaunchy Firmware Loader
- AMD-SB-4013: AMD Athlon and AMD Ryzen Processor Vulnerabilities - February 2026
- AMD-SB-7044: Physical Attacks Leading to Bypass of ASP Boot ROM Secure Boot
- AMD-SB-5007: AMD Embedded Vulnerabilities - August 2025
- AMD-SB-4012: AMD Client Vulnerabilities - August 2025
- AMD-SB-4011: TPM Reference Implementation
- AMD-SB-7039: Unauthorized Access to AMD Secure Processor's Crypto-Co-Processor
- AMD-SB-6008: AMD Graphics Driver Vulnerabilities - February 2025
- AMD-SB-5004: AMD Embedded Processors Vulnerabilities - February 2025
- AMD-SB-4008: AMD Client Processor Vulnerabilities - February 2025
- AMD-SB-5002: AMD Embedded Processors Vulnerabilities - Aug 2024
- AMD-SB-4004: Client Vulnerabilities - Aug 2024
- AMD-SB-3003: AMD Server Vulnerabilities - August 2024
- AMD-SB-5001: AMD Embedded Processors Vulnerabilities - February 2024
- AMD-SB-4002: AMD Client Vulnerabilities - November 2023
- AMD-SB-3002: AMD Server Vulnerabilities - Nov 2023
- AMD-SB-4005: fTPM Voltage Fault Injection
- AMD-SB-7002: TPM Out of Bounds Access
- AMD-SB-4001: Client Vulnerabilities - May 2023
- AMD-SB-3001: AMD Server Vulnerabilities - May 2023
- AMD-SB-1032: AMD Server Vulnerabilities - January 2023
- AMD-SB-1031: AMD Client Vulnerabilities - January 2023
- AMD-SB-1029: AMD Graphics Driver Vulnerabilities - November 2022
- AMD-SB-1028: AMD Server Vulnerabilities - May 2022
- AMD-SB-1027: AMD Client Vulnerabilities - May 2022
- AMD-SB-1021: AMD Server Vulnerabilities - November 2021