CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-16
ROUTINECVE-2025-54518updatedNATOA2vulnerability

AMD-SB-7052 / CVE-2025-54518: AMD Zen 2 op-cache corruption lets local code run instructions at a higher privilege, guest to host included (CVSS 7.3); OS updates on EPYC 7002, OEM BIOS updates on Ryzen

AMD Zen 2 op-cache flaw lets local code escalate privilege, guest to host included; Ryzen needs OEM BIOS updates

Analysis

AMD disclosed on 2026-05-12 that improper isolation of shared resources in the CPU operation cache of Zen 2-based products can cause incorrect instructions to execute at a higher privilege level; it scores CVE-2025-54518 at 7.3 on CVSS 4.0, with local access, high attack complexity and low privileges, and found it internally (AMD Product Security, 2026-05-12). Xen says code of any privilege could escalate, including userspace to kernel and guest to host, that only AMD Fam17h (Zen 2) CPUs are believed vulnerable, that all Xen versions are affected and that there is no mitigation other than its patches (Xen Project, 2026-05-12). Microsoft lists the flaw as not exploited or publicly disclosed and rates it Exploitation Unlikely, and says the latest Windows builds enable the mitigation (MSRC, CVE-2025-54518).

The fix depends on the product line: for EPYC 7002 and EPYC Embedded 7002 processors AMD's mitigation is an OS update from the OS vendor, while for Ryzen 3000, 4000, 5000, 7020 and 7030 series, Threadripper PRO 3000 WX and Ryzen Embedded V2000 AMD released Platform Initialization firmware to OEMs between October and December 2025, to be installed as an OEM BIOS update, for example ComboAM4v2 PI version 1.2.0.10 for Ryzen 3000, 4000 and 5000 desktop parts (AMD Product Security, 2026-05-12). NCSC-NL lists updates from Debian (Xen), Dell PowerEdge, Fedora, Google Cloud Platform, Lenovo and Microsoft Windows (NCSC-NL, 2026-05-15).

Cited evidence

AMD has identified a vulnerability in the CPU operation (op/µop) cache on Zen 2‑based products that can cause incorrect instructions to be executed at a higher privilege level.

AMD recommends updating to the Platform Initialization (PI) version indicated below.

AMD Product Security 2026-05-12

Code of any privilege could escalate to a higher privilege, including userspace to kernel, and guest to host.

Xen Project

This CVE is being documented in the Security Update Guide to announce that the latest builds of Windows enable the mitigation and provide protection against the vulnerability.

Microsoft Security Response Center 2026-05-12

Updates1

Correction

The mitigation does not ship as microcode in a Windows update for every affected chip: AMD lists an OS update only for EPYC 7002 and EPYC Embedded 7002 processors, and for Ryzen 3000 to 7030 series, Threadripper PRO 3000 WX and Ryzen Embedded V2000 it recommends the Platform Initialization versions in its table, delivered as OEM BIOS updates (AMD Product Security, 2026-05-12). Microsoft says the latest Windows builds enable the mitigation, not that they carry it for all processors (MSRC, CVE-2025-54518), so a Windows build check cannot confirm a Ryzen host is protected, and a processor-ID query reports the CPU model rather than whether the mitigation is in place.

NCSC-NL lists Fedora and Lenovo among the vendors with updates (NCSC-NL, 2026-05-15).

Sources4

Revision history

  1. Published 2026-05-16-5bc123a0
  2. Correction 2026-10-21T1148Z-audit

    AMD lists an OS update as the mitigation for CVE-2025-54518 only for EPYC 7002 and EPYC Embedded 7002 processors, and for Ryzen, Threadripper PRO and Ryzen Embedded V2000 parts OEM BIOS updates carrying the Platform Initialization versions in its table; Microsoft says the latest Windows builds enable a mitigation for the affected AMD models without naming them. NCSC-NL lists Fedora and Lenovo among the vendors with updates.

    Changed: actions affected_products body classification cves event_date evidence headline sources sourcing_note summary techniques title priority

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.