CVE-2025-54514VulnerabilityPublished 10 Feb 2026

CVE-2025-54514: AMD EPYC™ 9005 Series Processors · SoC

Affects AMD EPYC™ 9005 Series ProcessorsSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

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

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

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Local: The vulnerable system 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 through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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-26.

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

Affected software

Product	Affected	Fixed in
AMDAMD EPYC™ 9005 Series Processors	Affected–	Fixed in–
AMDAMD Ryzen™ 9000HX Series Processors	Affected–	Fixed in–
AMDAMD Ryzen™ AI 300 Series Processors	Affected–	Fixed in–
AMDAMD Ryzen™ 9000 Series Desktop Processors	Affected–	Fixed in–
AMDAMD Ryzen™ AI Max 300 Series Processors	Affected–	Fixed in–
AMDAMD Ryzen™ Z2 Series Processors Extreme	Affected–	Fixed in–
AMDAMD Ryzen™ AI 400 Series Processors	Affected–	Fixed in–
AMDAMD Ryzen™ Threadripper™ 9000 Processors	Affected–	Fixed in–
AMDAMD Ryzen™ Threadripper™ PRO 9000 WX-Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ Embedded 9005 Series Processors	Affected–	Fixed in–

AI-suggested

1. Enforce strict access controls and privilege management to limit local elevated access to trusted personnel and processes only. 2. Monitor systems for unusual local activity or privilege escalations that could indicate exploitation attempts. 3. Implement hardware-level security features such as AMD’s Secure Encrypted Virtualization (SEV) and ensure firmware is up to date. 4. Segregate critical workloads and sensitive data to minimize the impact of potential integrity breaches. 5. Engage with AMD and monitor for official patches or microcode updates addressing this vulnerability and apply them promptly once available. 6. Conduct regular security audits and penetration testing focusing on local privilege escalation and SoC resource isolation. 7. Consider deploying runtime integrity verification tools that can detect unauthorized changes in system state or memory. 8. Educate system administrators about the risks of local privilege misuse and the importance of maintaining strict operational security.

Description

Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

Impact

For European organizations, especially those operating critical infrastructure, cloud services, and data centers using AMD EPYC 9005 processors, this vulnerability poses a risk of integrity compromise. An attacker with local elevated privileges could manipulate or corrupt data or system states, potentially undermining trust in system operations or leading to further exploitation. While confidentiality and availability are not directly impacted, integrity loss can have cascading effects on business processes, compliance, and security posture. The risk is heightened in multi-tenant environments where shared hardware resources are common. Given the medium severity and the requirement for local privileged access, the threat is more relevant to internal threat actors or attackers who have already gained some foothold. The absence of known exploits reduces immediate risk but does not eliminate the need for vigilance. Organizations relying on AMD EPYC 9005 processors in Europe should assess their exposure, especially in sectors like finance, telecommunications, and government, where data integrity is critical.

CWE-1189Improper Isolation of Shared Resources on System-on-a-Chip (SoC) (opens in a new tab)
Base weakness
The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.
Architecture and Design · Separation of Privilege
When sharing resources, avoid mixing agents of varying trust levels.
Attack patterns
Shared Resource Manipulation (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

Affected software

Description

AI analysisMachine-generated, updated 18 Feb 2026, 10:10 UTC

WeaknessesCWE-1189

Technical details

References

Community reviews

Related threats