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-2025-0012: CWE-1260 Improper Handling of Overlap Between Protected Memory Ranges in AMD AMD EPYC™ 9005 Series Processors

0
Medium
VulnerabilityCVE-2025-0012cvecve-2025-0012cwe-1260
Published: Tue Feb 10 2026 (02/10/2026, 19:12:24 UTC)
Source: CVE Database V5
Vendor/Project: AMD
Product: AMD EPYC™ 9005 Series Processors

Description

Improper handling of overlap between the segmented reverse map table (RMP) and system management mode (SMM) memory could allow a privileged attacker corrupt or partially infer SMM memory resulting in loss of integrity or confidentiality.

AI-Powered Analysis

AILast updated: 02/10/2026, 20:06:37 UTC

Technical Analysis

CVE-2025-0012 is a vulnerability identified in AMD EPYC™ 9005 Series processors related to improper handling of overlapping protected memory regions, specifically between the segmented reverse map table (RMP) and system management mode (SMM) memory. The RMP is a hardware mechanism used to enforce memory protections, while SMM is a highly privileged execution mode used for low-level system management tasks, including firmware and hardware control. The vulnerability arises because the processor does not correctly handle cases where the RMP and SMM memory regions overlap, allowing a privileged attacker to corrupt or partially infer the contents of SMM memory. This can lead to loss of confidentiality and integrity of sensitive system management data, potentially undermining the trustworthiness of firmware operations and system security. Exploitation requires high privileges (e.g., administrative or root access) but does not require user interaction. The vulnerability has a CVSS 4.0 base score of 6.8, indicating medium severity. No known exploits have been reported in the wild, and no patches have been released yet. The flaw is tracked under CWE-1260, which relates to improper handling of overlapping protected memory ranges. This vulnerability is particularly concerning for environments where AMD EPYC 9005 processors are deployed in critical infrastructure, cloud, or enterprise server contexts, as compromise of SMM memory could facilitate stealthy attacks or persistent firmware manipulation.

Potential Impact

For European organizations, the impact of CVE-2025-0012 could be significant in sectors relying heavily on AMD EPYC 9005 processors, such as cloud service providers, data centers, telecommunications, and critical infrastructure. Successful exploitation could allow attackers with privileged access to compromise the integrity and confidentiality of system management memory, potentially enabling persistent firmware-level attacks or unauthorized disclosure of sensitive system information. This undermines trust in platform security and could facilitate further lateral movement or privilege escalation within affected networks. Although exploitation requires high privileges, insider threats or attackers who have already gained administrative access could leverage this vulnerability to deepen their control and evade detection. The absence of patches increases risk exposure until mitigations or firmware updates are available. Given the strategic importance of secure server infrastructure in European digital economies and critical services, this vulnerability poses a moderate but non-negligible risk to operational continuity and data protection compliance.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict and monitor administrative access rigorously to prevent attackers from obtaining the high privileges required to exploit this vulnerability. 2) Employ strict access controls and segmentation to limit the scope of privileged accounts and reduce insider threat risks. 3) Monitor system logs and firmware integrity indicators for anomalies that could suggest attempts to manipulate SMM memory. 4) Engage with AMD and hardware vendors to obtain timely firmware updates or microcode patches addressing this vulnerability as soon as they become available. 5) Consider deploying hardware-based security features such as Trusted Platform Modules (TPM) and secure boot mechanisms to detect unauthorized firmware modifications. 6) In cloud or multi-tenant environments, enforce strong tenant isolation and hypervisor security to reduce risk of privilege escalation. 7) Conduct regular security audits and penetration testing focused on privileged access paths and firmware security. 8) Maintain up-to-date incident response plans that include scenarios involving firmware or hardware-level compromise. These targeted actions go beyond generic patching advice and focus on reducing the likelihood of exploitation and detecting attempts early.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
AMD
Date Reserved
2024-10-10T20:27:48.525Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 698b8b0b4b57a58fa1266766

Added to database: 2/10/2026, 7:46:19 PM

Last enriched: 2/10/2026, 8:06:37 PM

Last updated: 2/21/2026, 12:22:17 AM

Views: 54

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