Skip to main content
VulnerabilityPublished

CVE-2025-29939: AMD EPYC™ 9004 Series Processors · Improper Access Control

Affects AMD EPYC™ 9004 Series ProcessorsSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score
6.9Medium
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:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AMDAMD EPYC™ 9004 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 7003 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 9005 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 8004 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 7003 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa")Affected–Fixed in–

AI-suggested

  1. Monitor AMD and relevant vendor advisories closely for patches or microcode updates addressing this vulnerability and apply them promptly once available.
  2. Restrict and harden access to host systems and hypervisors to prevent attackers from gaining the high privileges required to exploit this flaw.
  3. Employ strict access controls, multi-factor authentication, and continuous monitoring on virtualization hosts.
  4. Consider disabling SEV or SNP features temporarily if feasible and if risk tolerance allows, until patches are applied.
  5. Use runtime security tools that can detect anomalous memory access patterns or unauthorized modifications to critical data structures like the RMP.
  6. Conduct regular security audits and penetration testing focused on virtualization security controls.
  7. Segment and isolate critical workloads to limit potential lateral movement in case of host compromise.
  8. Collaborate with cloud providers to understand their mitigation strategies if using hosted services running on AMD EPYC 9004 processors.
  9. Maintain up-to-date inventory of hardware and virtualization features in use to prioritize risk assessment and response.

Description

Improper access control in secure encrypted virtualization (SEV) could allow a privileged attacker to write to the reverse map page (RMP) during secure nested paging (SNP) initialization, potentially resulting in a loss of guest memory confidentiality and integrity.

References

Community reviews

Loading reviews…