CVE Intelligence
High

CVE-2025-54518 — Improper isolation of shared resources within the CPU operation cache on Zen 2-based…

Improper isolation of shared resources within the CPU operation cache on Zen 2-based products could allow an attacker to corrupt instructions executed at a different privilege level, potentially resulting in privilege escalation.

Published May 15, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: AMD

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.29%
ahead of 20% of scored CVEs · Oct 14, 2026
Affects
AMD
AMD EPYC™ 7002 Series Processors and 11 more
CVSS base
7.0
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (AMD AMD EPYC™ 7002 Series Processors, AMD AMD EPYC™ Embedded 7002 Series Processors, AMD AMD Ryzen Embedded V2000A Series Processors…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
AMD AMD EPYC™ 7002 Series Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD EPYC™ Embedded 7002 Series Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen Embedded V2000A Series Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 3000 Series Desktop Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 4000 Series Desktop Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ Embedded V2000 Series Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Ryzen™ Threadripper™ PRO 3000 WX-Series Processors versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.3 CVSS 4.0 High — — psirt@amd.com via NIST National Vulnerability Database
7.3 CVSS 4.0 High — — AMD via CVE Program (cve.org) e CISA ADP
7.0 CVSS 3.1 High 1.0 5.9 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1189

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · amd/amd epyc™ 7002 series processors, amd/amd ryzen™ 4000 series mobile processors with radeon™ graphics, amd/amd ryzen™
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.0
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 15, 2026 · AMD

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

21 on the record

Elsewhere on this site

AMD
every CVE for this vendor
CWE-1189
other pages naming this weakness

Related CVEs (same products)

  • CVE-2023-20540 An observable timing discrepancy in the ASP could allow a privileged attacker to perform… Jun 26, 2026
  • CVE-2023-20572 An observable timing discrepancy in the ASP could allow a privileged attacker to perform… Jun 26, 2026
  • CVE-2021-46747 Insufficient granularity of access control in ASP (AMD Secure Processor) may allow an… Jun 1, 2026
  • CVE-2025-48516 Incorrect Default Permissions in AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics May 15, 2026
  • CVE-2023-31316 Improperly preserved integrity of hardware configuration state during a power… May 15, 2026
  • CVE-2021-26380 Integer Overflow or Wraparound in AMD AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics May 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-54518 is "Improper isolation of shared resources within the CPU operation cache on Zen 2-based…", rated High. It affects AMD EPYC™ 7002 Series Processors (AMD); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.