CVE-2024-36331VulnerabilityPublished 6 Sep 2025Updated 3 Nov 2025

CVE-2024-36331: AMD EPYC™ 9004 Series Processors · Improper Initialization

Affects AMD EPYC™ 9004 Series ProcessorsSource CVE Database V5

Not known to be exploited · CVSS 3.2 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.2Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Restrict hypervisor access strictly to trusted administrators and implement strong multi-factor authentication to reduce the risk of privilege escalation. 2. Monitor hypervisor activity and audit logs for unusual behavior that could indicate attempts to exploit this vulnerability. 3. Employ hardware-based security features and firmware updates from AMD as soon as patches or mitigations become available. 4. Consider isolating critical workloads on separate physical hosts or using alternative virtualization technologies until a fix is released. 5. Regularly update and patch hypervisor software and related management tools to minimize the risk of initial compromise. 6. Implement robust incident response plans to quickly detect and respond to hypervisor-level breaches. 7. Engage with AMD and cloud service providers to stay informed about updates and recommended configurations related to SEV-SNP security. 8. Conduct security assessments and penetration testing focused on hypervisor security to identify potential weaknesses before attackers do.

Description

Improper initialization of CPU cache memory could allow a privileged attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity.

Impact

For European organizations, the primary impact of CVE-2024-36331 lies in environments that deploy AMD EPYC 9004 Series processors with SEV-SNP enabled virtualization technology. These environments typically include cloud service providers, data centers, and enterprises running sensitive workloads in virtual machines. The vulnerability allows a privileged attacker controlling the hypervisor to overwrite guest memory, leading to potential data corruption or manipulation within virtual machines. This undermines the integrity of guest workloads, which could affect applications relying on secure virtualization for confidentiality and integrity guarantees. Although confidentiality and availability are not directly impacted, the loss of data integrity can have serious consequences for compliance, auditing, and trust in cloud services. European organizations in sectors such as finance, healthcare, and government, which often use secure virtualization to protect sensitive data, may face increased risk if hypervisor security is compromised. The requirement for hypervisor-level privileges limits the attack surface to insider threats or attackers who have already breached host controls. However, given the growing adoption of AMD EPYC processors in European data centers, the potential for exploitation exists if proper controls are not maintained.

CWE-665Improper Initialization (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
Implementation
Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 18:03 UTC

WeaknessesCWE-665

Technical details

References

Community reviews

Related threats