Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-36354: CWE-1231 - Improper Prevention of Lock Bit Modification in AMD AMD Ryzen™ Threadripper™ 3000 Processors

0
High
VulnerabilityCVE-2024-36354cvecve-2024-36354cwe-1231
Published: Sat Sep 06 2025 (09/06/2025, 18:06:43 UTC)
Source: CVE Database V5
Vendor/Project: AMD
Product: AMD Ryzen™ Threadripper™ 3000 Processors

Description

Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root of Trust for BIOS update, to bypass SMM isolation potentially resulting in arbitrary code execution at the SMM level.

AI-Powered Analysis

AILast updated: 02/26/2026, 20:13:05 UTC

Technical Analysis

CVE-2024-36354 is a vulnerability categorized under CWE-1231 (Improper Prevention of Lock Bit Modification) found in AMD Ryzen™ Threadripper™ 3000 processors. The root cause is improper input validation of the DIMM Serial Presence Detect (SPD) metadata. SPD is a small EEPROM on memory modules that stores information about the module's size, speed, voltage, and timings. This vulnerability allows an attacker who has physical access to the machine, ring0 (kernel-level) privileges on a system with a non-compliant DIMM, or control over the BIOS update Root of Trust, to manipulate SPD data in a way that bypasses the isolation mechanisms of the System Management Mode (SMM). SMM is a highly privileged CPU mode used for low-level system management and firmware operations, isolated from the operating system and other software layers. By bypassing SMM isolation, an attacker can execute arbitrary code at the SMM level, gaining control over critical system functions, potentially persisting across reboots and evading detection by conventional security mechanisms. The vulnerability has a CVSS v3.1 score of 7.5, reflecting high impact on confidentiality, integrity, and availability, but requires high privileges and physical or ring0 access, limiting the attack surface. No public patches or exploits are currently available, but the risk remains significant due to the privileged nature of SMM and the potential for stealthy, persistent compromise.

Potential Impact

The exploitation of CVE-2024-36354 can have severe consequences for organizations globally. Successful attacks could lead to full system compromise at the firmware level, allowing attackers to bypass operating system security controls and persist undetected. This can result in theft of sensitive data, manipulation of system operations, installation of persistent malware, and disruption of critical services. Environments with high-value targets such as data centers, cloud providers, financial institutions, and government agencies are particularly at risk. The requirement for physical or ring0 access limits remote exploitation but does not eliminate risk in scenarios involving insider threats, supply chain attacks, or sophisticated adversaries capable of firmware manipulation. The vulnerability undermines the trustworthiness of the hardware root of trust and firmware security, potentially impacting the security posture of systems relying on AMD Threadripper 3000 processors for critical workloads.

Mitigation Recommendations

To mitigate CVE-2024-36354, organizations should: 1) Ensure strict physical security controls to prevent unauthorized access to systems with affected processors. 2) Maintain up-to-date firmware and BIOS versions from AMD and system vendors, monitoring for patches addressing this vulnerability. 3) Validate and restrict BIOS update mechanisms to trusted sources only, enforcing cryptographic verification of firmware images to protect the Root of Trust. 4) Use memory modules compliant with AMD specifications to avoid non-compliant DIMMs that could be exploited. 5) Employ runtime integrity monitoring and hardware-based security features such as TPM and Secure Boot to detect unauthorized firmware modifications. 6) Limit ring0 access to trusted administrators and use endpoint protection solutions capable of detecting anomalous kernel-level activities. 7) Conduct regular security audits and penetration tests focusing on firmware and hardware security layers. 8) Collaborate with AMD and hardware vendors for guidance and early access to patches or mitigations as they become available.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
AMD
Date Reserved
2024-05-23T19:44:50.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a0a1cc85912abc71d0bd13

Added to database: 2/26/2026, 7:41:00 PM

Last enriched: 2/26/2026, 8:13:05 PM

Last updated: 2/27/2026, 1:56:49 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses