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-36354 Overview
CVE-2024-36354 is an improper input validation vulnerability affecting AMD platforms that parse DIMM Serial Presence Detect (SPD) metadata. The flaw allows an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root of Trust for a BIOS update to bypass System Management Mode (SMM) isolation. Successful exploitation can lead to arbitrary code execution at the SMM level, which operates below the operating system and hypervisor. The weakness is categorized under CWE-1231: Improper Prevention of Lock Bit Modification.
Critical Impact
Arbitrary code execution at SMM level breaks the firmware trust boundary, enabling persistent, hypervisor-invisible compromise of the platform.
Affected Products
- AMD platforms referenced in AMD Security Bulletin SB-3014
- AMD platforms referenced in AMD Security Bulletin SB-4012
- AMD platforms referenced in AMD Security Bulletin SB-5007
Discovery Timeline
- 2025-09-06 - CVE-2024-36354 published to the National Vulnerability Database
- 2026-06-17 - Last updated in the NVD database
Technical Details for CVE-2024-36354
Vulnerability Analysis
The vulnerability resides in firmware code paths that read and process DIMM Serial Presence Detect (SPD) metadata during platform initialization. SPD is a standardized data structure stored on an EEPROM on each memory module and consumed by the BIOS to configure memory timings, geometry, and training parameters. Firmware trusts SPD content when calculating memory layout and when transitioning data structures into System Management RAM (SMRAM). Improper validation of SPD fields allows crafted values to influence SMM data structures and control flow. Because SMM executes at the highest firmware privilege level, a successful bypass of SMM isolation gives the attacker execution context above the operating system and hypervisor.
Root Cause
The root cause is improper input validation of attacker-controlled SPD metadata consumed by code reachable from or shared with SMM handlers. The firmware does not fully constrain SPD-derived values before using them in logic that affects SMM-protected regions, violating the trust boundary described in CWE-1231.
Attack Vector
Three exploitation paths exist. First, an attacker with physical access can install a non-compliant DIMM programmed with crafted SPD contents. Second, an attacker with ring0 privileges on a system already containing a non-compliant DIMM can trigger SMM entry paths that consume the malicious metadata. Third, an attacker in control of the Root of Trust for BIOS update can deliver firmware that mishandles SPD processing. The vulnerability requires local access and high privileges, with high attack complexity.
No verified proof-of-concept code is publicly available. Refer to the AMD
security bulletins (SB-3014, SB-4012, SB-5007) for affected processor
families and firmware remediation guidance.
Detection Methods for CVE-2024-36354
Indicators of Compromise
- Unexpected changes to installed BIOS/UEFI version strings or firmware capsule hashes outside of sanctioned update windows.
- Presence of DIMMs reporting malformed, out-of-spec, or non-JEDEC-compliant SPD fields during platform inventory.
- Unexplained SMI (System Management Interrupt) activity or SMM handler modifications observed through platform telemetry.
Detection Strategies
- Compare SPD contents of installed memory modules against vendor-published reference values and JEDEC specifications.
- Monitor firmware measurements via TPM PCR values and attestation services to detect unauthorized changes to the Root of Trust for Update.
- Correlate ring0 driver loads and SMI invocation rates with hardware inventory changes to identify suspicious SMM entry patterns.
Monitoring Recommendations
- Enroll endpoints in a platform firmware integrity attestation service and alert on PCR drift.
- Track BIOS/UEFI versions in the asset inventory and flag systems running firmware older than the AMD-provided remediation levels.
- Audit administrative actions that invoke BIOS update utilities or modify Secure Boot and firmware update policies.
How to Mitigate CVE-2024-36354
Immediate Actions Required
- Inventory AMD-based systems and identify platforms covered by AMD Security Bulletin SB-3014, SB-4012, and SB-5007.
- Apply the AGESA and OEM BIOS updates provided by the system vendor for each affected platform.
- Restrict physical access to servers and workstations and enforce chassis intrusion detection where available.
- Limit ring0 driver installation to signed, vetted drivers and remove unused kernel-mode components.
Patch Information
AMD has published firmware remediation guidance in the referenced security bulletins. OEMs integrate the fixes into vendor-specific BIOS releases. Administrators should obtain BIOS updates from the system manufacturer and verify that the installed version matches or exceeds the minimum remediated version listed in the applicable AMD bulletin.
Workarounds
- Procure DIMMs only from authorized channels and validate SPD contents against vendor references before deployment.
- Enforce Secure Boot and platform firmware update policies that require signed capsules from the OEM Root of Trust.
- Where firmware updates cannot be applied immediately, restrict local administrator rights to reduce the pool of accounts able to reach ring0 and SMM entry paths.
# Example: enumerate installed memory and firmware version on Linux
sudo dmidecode -t memory | grep -E 'Manufacturer|Part Number|Serial'
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date
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

