Processor vulnerability
CVE-2025-54509
A hypervisor could switch the Secure Processor's memory accesses to non-coherent, so that it read stale DRAM and lost recent writes of an SEV-SNP guest.
- Name
- Non-coherent Secure Processor memory access
- Vulnerability
- AMD Secure Processor and SMU firmware
- Kind
- Firmware
- CVE published
- 2026-06-09 CVE record
- Advisories
- AMD-SB-3039
Benedict Schlueter and Shweta Shinde of ETH Zurich found that a
system setting the hypervisor controls decides whether the AMD
Secure Processor’s memory requests stay coherent with the CPU
caches. With coherency off, the Secure Processor can read stale data
from DRAM while it copies pages and updates their metadata, so
writes a guest still holds in the caches are lost, which undermines
the integrity of SEV-SNP guests. AMD’s record puts the flaw in the
access control of an IOMMU register interface. It affects the fourth
and fifth EPYC generations; exploiting it needs a malicious
hypervisor and precise timing.What the sources say of each microarchitecture.
Affected processors
2 of the 2 microarchitectures listed are affected in all or some of their models.
Mitigations
- Firmware: GenoaPI 1.0.0.H, TurinPI 1.0.0.8, EmbGenoaPI-SP5 1.0.0.D and EmbeddedTurinPI_SP5 1004, from late 2025 and 2026. Source.
Related CVEs
- CVE-2018-8930 Hardware Validated Boot bypass (MASTERKEY)
- CVE-2018-8931 Secure Processor access from x86 (RYZENFALL-1)
- CVE-2018-8932 Secure Processor access from x86 (RYZENFALL-2 to 4)
- CVE-2018-8933 Protected memory regions on EPYC (FALLOUT)
- CVE-2018-8934 Promontory chipset firmware (CHIMERA-FW)
- CVE-2018-8935 Promontory chipset hardware (CHIMERA-HW)
- CVE-2018-8936 Secure Processor privilege escalation
- CVE-2020-12926 fTPM failed-shutdown counting
- CVE-2020-12930 Secure Processor driver parameters
- CVE-2020-12931 Secure Processor kernel parameters
- CVE-2020-12944 BIOS image length check
- CVE-2020-12946 Discrete TPM command input
- CVE-2020-12951 Race into ASP SMM operations
- CVE-2020-12961 Zeroing System Management Network registers
- CVE-2021-26315 Encrypted firmware integrity in the boot ROM
- CVE-2021-26322 IV reuse for the platform private key
- CVE-2021-26329 SMU integer overflow
- CVE-2021-26330 SMU heap overflow
- CVE-2021-26331 SMU mailbox entries
- CVE-2021-26335 Bootloader image header checks
- CVE-2021-26336 SMU bounds checks
- CVE-2021-26337 SMU DMA from bad DRAM addresses
- CVE-2021-26338 SMU performance control tables
- CVE-2021-26343 ASP BIOS and DRTM commands
- CVE-2021-26344 Out-of-bounds write in the APCB
- CVE-2021-26345 APCB token value
- CVE-2021-26346 L2 directory integer overflow (2023)
- CVE-2021-26347 L2 directory integer overflow (2022)
- CVE-2021-26350 SMU message port race
- CVE-2021-26351 SMU DMA to bad DRAM addresses
- CVE-2021-26352 SMU PCIe hot plug table
- CVE-2021-26353 DRTM user application left half set up
- CVE-2021-26354 Zeroing memory from a compromised ABL
- CVE-2021-26355 SMU message port registers
- CVE-2021-26356 SPI ROM changed after it is read
- CVE-2021-26361 Memory exfiltration from the stage 2 bootloader
- CVE-2021-26362 Mapping SMN registers from a user application
- CVE-2021-26363 Moving the ASP's reserved DRAM
- CVE-2021-26364 SMU mailbox register bounds
- CVE-2021-26365 Size values in firmware headers
- CVE-2021-26366 Boot ROM readout
- CVE-2021-26367 Trusted memory region setup from x86
- CVE-2021-26368 Trusted OS process type check
- CVE-2021-26369 Malformed bootloader system call
- CVE-2021-26370 Firmware load destination address
- CVE-2021-26371 SHA256 system call exposes ASP memory
- CVE-2021-26372 SMU PCIe bounds checks
- CVE-2021-26373 SMU voltage malfunction
- CVE-2021-26375 SMU GPIO bounds checks
- CVE-2021-26376 SMU FeatureConfig
- CVE-2021-26377 Trusted OS process space overflow
- CVE-2021-26378 SMU address bounds checks
- CVE-2021-26379 SMU mailbox corrupts SMRAM
- CVE-2021-26380 Malformed call from a Trusted OS driver
- CVE-2021-26381 Trusted OS mapping system call
- CVE-2021-26383 AMD TEE command bounds
- CVE-2021-26386 Malformed call to the stage 2 bootloader
- CVE-2021-26387 ASP kernel DRAM mapping
- CVE-2021-26390 Bootloader corrupts memory for a user application
- CVE-2021-26392 LoadModule size check
- CVE-2021-26393 TEE memory not cleared
- CVE-2021-26397 Address validation for ABL and user application
- CVE-2021-26398 SYS_KEY_DERIVE system call
- CVE-2021-26407 Random IV collisions
- CVE-2021-26410 ASP kernel reads its own memory as parameters
- CVE-2021-46746 No stack protection in the ASP Secure OS
- CVE-2021-46747 Mapping SMN apertures from user space
- CVE-2021-46749 SMI mailbox checksum read
- CVE-2021-46750 Graphics mailbox overlaps a TMR
- CVE-2021-46753 Sensor fusion hub header lengths
- CVE-2021-46754 Bootloader leaks to the SMU
- CVE-2021-46755 SysHub mappings left in error paths
- CVE-2021-46756 SVC_MAP_USER_STACK input
- CVE-2021-46757 Secure OS kernel memory from a TA
- CVE-2021-46758 SPI flash addresses in the bootloader
- CVE-2021-46759 TEE memory to the serial port
- CVE-2021-46760 Out-of-bounds bootloader system call
- CVE-2021-46762 SMU SRAM corruption
- CVE-2021-46763 SMU shared buffer overflow
- CVE-2021-46764 SMU overwrites ASP memory
- CVE-2021-46765 ASP reads from a compromised SMM
- CVE-2021-46766 Keys left in bootloader SRAM
- CVE-2021-46767 ASP writes from physical access
- CVE-2021-46769 Arbitrary DMA copies from the bootloader
- CVE-2021-46771 ASP firmware system call addresses
- CVE-2021-46772 ABL and SPI ROM structure headers
- CVE-2021-46773 ABL corrupts ASP memory
- CVE-2021-46774 SMU DRAM address checks
- CVE-2021-46775 ABL memory overwrite with physical access
- CVE-2021-46779 SVC_ECC_PRIMITIVE system call
- CVE-2021-46791 SMM binary corrupts DRTM memory
- CVE-2021-46792 BIOS2PSP race on S3 resume
- CVE-2021-46794 SMI mailbox checksum read (second CVE)
- CVE-2021-46795 TEE OS reads out of bounds
- CVE-2022-23815 APCB out-of-bounds write
- CVE-2022-23817 Secure OS kernel memory from a TA
- CVE-2023-20507 ASP integer overflow
- CVE-2023-20508 ASP out-of-bounds write
- CVE-2023-20515 fTPM driver in the Trusted OS
- CVE-2023-20518 Master Encryption Key left in memory
- CVE-2023-20520 Bootloader return address
- CVE-2023-20521 SPI ROM records changed after verification
- CVE-2023-20522 ASP input from a malicious BIOS
- CVE-2023-20523 ASP buffer overflow with physical access
- CVE-2023-20524 Malformed commands to another socket's ASP
- CVE-2023-20525 Bootloader reads beyond a mapped register
- CVE-2023-20526 ASP memory exposed with physical access
- CVE-2023-20527 Bootloader out-of-bounds read
- CVE-2023-20528 SMU memory over I2C
- CVE-2023-20529 SMU from/to addresses
- CVE-2023-20530 SMU BIOS mailbox messages
- CVE-2023-20531 SMU SRAM from/to addresses
- CVE-2023-20532 SMU resource locking
- CVE-2023-20533 SMU DRAM addresses (2023)
- CVE-2023-20540 HMAC timing in the ASP
- CVE-2023-20572 HMAC timing in the ASP (client)
- CVE-2023-20589 Voltage fault injection on fTPM secure boot
- CVE-2023-20591 IOMMU not reset at a DRTM event
- CVE-2023-20599 Crypto Co-Processor registers from x86
- CVE-2023-31316 VCN firmware flow after power save
- CVE-2023-31325 PSP reserved DRAM tampering
- CVE-2023-31326 Leftover TEE driver data
- CVE-2023-31330 ASP out-of-bounds read from a bootloader
- CVE-2023-31331 DRTM driver initialized twice
- CVE-2024-21970 Power management firmware array index
- CVE-2024-21981 ASP key usage control
- CVE-2025-0044 Power management firmware read
- CVE-2025-29949 Bootloader legacy recovery mode
- CVE-2025-29951 Bootloader buffer overflow
- CVE-2025-48515 Bootloader input on SPI ROM upgrade
- CVE-2025-48516 DDR5 PMIC left unprotected