Skip to main content
Vulnerability Database/CVE-2024-21925

CVE-2024-21925: AMD PSP Driver RCE Vulnerability

CVE-2024-21925 is a remote code execution vulnerability in the AMD PSP P2Cmbox driver that allows privileged attackers to overwrite SMRAM and execute arbitrary code. This article covers technical details, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-21925 Overview

CVE-2024-21925 is an improper input validation vulnerability [CWE-20] in the AMD AmdPspP2CmboxV2 driver. The flaw allows a privileged local attacker to overwrite System Management RAM (SMRAM), which can lead to arbitrary code execution in System Management Mode (SMM). SMM runs at a higher privilege level than the operating system kernel, so successful exploitation effectively bypasses OS-level security controls, including Secure Boot and hypervisor protections.

Critical Impact

Successful exploitation grants code execution in SMM, giving the attacker ring -2 persistence beneath the operating system and hypervisor.

Affected Products

  • AMD platform firmware shipping the AmdPspP2CmboxV2 Platform Security Processor (PSP) driver
  • UEFI firmware builds that integrate the vulnerable AMD PSP mailbox driver module
  • Refer to AMD Security Bulletin AMD-SB-7027 for the complete list of affected processors and firmware versions

Discovery Timeline

  • 2025-02-11 - CVE-2024-21925 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-21925

Vulnerability Analysis

The vulnerability resides in the AmdPspP2CmboxV2 driver, a UEFI DXE module responsible for mediating communication between the host and the AMD Platform Security Processor through a command mailbox. The driver fails to properly validate input parameters, including attacker-controlled pointers or length fields, before using them during SMI (System Management Interrupt) handling.

Because the driver executes within the SMM context, insufficient validation of caller-supplied data allows a privileged attacker to direct writes into SMRAM. SMRAM is a protected memory region reserved for System Management Mode handlers and is normally isolated from the operating system. Overwriting SMRAM contents permits the attacker to redirect SMI handler execution to attacker-controlled code.

Root Cause

The root cause is missing or incomplete bounds and pointer validation on data passed into the SMI handler exposed by AmdPspP2CmboxV2. SMM handlers must sanitize all input originating outside SMRAM, including communication buffer pointers and lengths. The driver does not enforce that destination addresses fall outside SMRAM, enabling a confused-deputy write primitive.

Attack Vector

Exploitation requires local access with high privileges, typically administrator or root. An attacker invokes the vulnerable SMI handler from the operating system by writing to the APMC port and preparing a crafted communication buffer. The handler then performs the unchecked write, corrupting SMRAM. Follow-on SMI invocations execute attacker-controlled code at SMM privilege. User interaction is not required, and the scope changes because SMM compromise affects the entire platform trust boundary.

No verified public proof-of-concept code is available for this issue. Technical details are published in AMD Security Bulletin AMD-SB-7027.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2024-21925

Indicators of Compromise

  • Unexpected firmware or UEFI variable modifications on AMD-based systems, particularly changes to SMM-related NVRAM variables
  • Unsigned or unexpected DXE modules present in firmware captures taken with tools such as CHIPSEC
  • Processes running with administrative privileges that interact with \\.\PhysicalMemory, MSR interfaces, or trigger APMC port writes to invoke SMIs

Detection Strategies

  • Perform offline firmware integrity verification by comparing SPI flash dumps against vendor-provided golden images
  • Use CHIPSEC modules such as common.smm and common.smrr to validate SMRAM lock status and detect handler tampering on affected AMD platforms
  • Monitor endpoints for privileged tools that load custom kernel drivers capable of issuing SMIs, which is a prerequisite for exploitation

Monitoring Recommendations

  • Enable firmware measurement to the TPM and audit PCR values for unexpected changes across reboots
  • Collect UEFI event logs and correlate boot-time anomalies with endpoint telemetry in a centralized data lake
  • Alert on new or unsigned kernel driver installations on systems running AMD processors covered by AMD-SB-7027

How to Mitigate CVE-2024-21925

Immediate Actions Required

  • Inventory AMD-based systems and cross-reference processor families against AMD Security Bulletin AMD-SB-7027
  • Apply firmware updates distributed by OEMs (Dell, HP, Lenovo, Supermicro, ASUS, and others) that incorporate the fixed AMD PSP firmware package
  • Restrict administrative privileges, since exploitation requires high-privilege local access to invoke the vulnerable SMI handler
  • Validate that Secure Boot, SMM Lock, and SMRR (SMM Range Registers) are enabled on all affected platforms

Patch Information

AMD has released updated AGESA firmware addressing the input validation flaw in the AmdPspP2CmboxV2 driver. The fix is distributed to system integrators and OEMs for inclusion in platform BIOS/UEFI updates. Consult AMD Security Bulletin AMD-SB-7027 for the minimum fixed firmware versions per processor family, then obtain the matching BIOS release from the system vendor.

Workarounds

  • No software-only workaround fully mitigates the vulnerability; firmware update is the authoritative fix
  • Reduce the local attack surface by limiting administrator accounts and enforcing application allow-listing to prevent loading of attacker kernel drivers
  • Enable measured boot and remote attestation where supported, so compromised firmware can be identified before trusted workloads are provisioned
bash
# Verify current BIOS/firmware version on Linux
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date

# Verify current BIOS version on Windows
wmic bios get smbiosbiosversion,releasedate

# Example: run CHIPSEC SMM checks (requires root/admin)
sudo chipsec_main -m common.smm
sudo chipsec_main -m common.smrr

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.