CVE-2025-54518: Improper isolation of shared resources within the CPU operation cache on Zen 2-based products could allow a...
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.
Security readout for executives and security teams
A flaw in AMD Zen 2 processors lets an attacker who already has a low-privilege foothold on a system corrupt instructions run at a higher privilege level, which could hand them administrator or kernel control. It affects a wide range of EPYC server, Ryzen desktop, mobile, Threadripper, and embedded CPUs. Fixes come from AMD as firmware/microcode updates delivered by system vendors and hypervisor updates from projects like Xen. Broad across AMD Zen 2 fleets: EPYC 7002 and Embedded 7002 servers, Ryzen 3000/4000 desktop, Ryzen 4000/5000/7020/7030 mobile with Radeon graphics, Threadripper PRO 3000WX, and Embedded V2000/V2000A. Multi-tenant hypervisor hosts and shared workstations are highest exposure. Treat as a scheduled but firm priority: not a drop-everything emergency, but Zen 2 servers—especially virtualization hosts and multi-tenant workloads—should be included in the next firmware and hypervisor maintenance window. Delay increases risk if a working local privilege escalation is published. Mitigation focus: Inventory Zen 2 systems against the AMD SB-7052 product list to scope exposure.; Apply vendor BIOS/UEFI updates containing the AGESA versions AMD lists per family.; Deploy OS microcode updates from Linux distributions and Windows once available..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1189: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1189 · source CWE mapping
Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
Improper Isolation of Shared Resources on System-on-a-Chip (SoC) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insufficient Granularity of Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.