CVE-2025-29946: AMD EPYC™ 9005 Series Processors · Insufficient or Incomplete Data Removal within Hardware Component
Affects AMD EPYC™ 9005 Series ProcessorsSource CVE Database V5
Not known to be exploited · CVSS 4.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- 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:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AMDAMD EPYC™ 9005 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ Embedded 9005 Series Processors | Affected– | Fixed in– |
AI-suggested
European organizations should implement strict access controls to limit administrative and privileged access to systems running AMD EPYC 9005 processors. Employ robust monitoring and auditing of privileged operations to detect suspicious activities. Isolate sensitive workloads and consider additional software-based memory isolation techniques to reduce reliance on hardware-level protections until patches are available. Engage with AMD and hardware vendors to obtain timely firmware updates or mitigations once released. Conduct thorough risk assessments for virtualized environments and consider temporary migration of critical workloads to unaffected hardware if feasible. Maintain up-to-date inventory of affected hardware and ensure that incident response teams are aware of the vulnerability specifics. Additionally, reinforce endpoint security and network segmentation to reduce the attack surface for local privilege escalation attempts.
Description
Insufficient or Incomplete Data Removal in Hardware Component in SEV firmware doesn't fully flush IOMMU. This can potentially lead to a loss of confidentiality and integrity in guest memory.