Skip to main content
CVE-2025-0031VulnerabilityPublished

CVE-2025-0031: AMD EPYC™ 9004 Series Processors · Use After Free

Affects AMD EPYC™ 9004 Series ProcessorsSource CVE Database V5

0

Not known to be exploited · CVSS 4.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/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 2026-10-25.

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 9003 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 9005 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 9004 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 8004 Series ProcessorsAffected–Fixed in–

AI-suggested

1. Restrict hypervisor administrative privileges strictly to trusted personnel and processes to reduce the risk of malicious hypervisor activity. 2. Enforce strict VM migration policies that prevent cross-socket migration of VMs configured with the SINGLE_SOCKET policy or disable such policies if not required. 3. Monitor VM migration logs and hypervisor events for unusual or unauthorized migration attempts, especially those involving socket changes. 4. Apply any forthcoming firmware or SEV firmware updates from AMD promptly once available to address this vulnerability. 5. Consider isolating critical workloads on dedicated sockets or physical hosts to minimize the attack surface related to socket migration. 6. Conduct regular security audits and penetration testing focused on hypervisor and VM migration security controls. 7. Collaborate with cloud service providers to ensure they have mitigations in place if using AMD EPYC 9004 processors. 8. Implement defense-in-depth strategies including hypervisor integrity monitoring and anomaly detection to identify potential exploitation attempts early.

Description

A use after free in the SEV firmware could allow a malicous hypervisor to activate a migrated guest with the SINGLE_SOCKET policy on a different socket than the migration agent potentially resulting in loss of integrity.

References

Community reviews

Loading reviews…