AMD and Google Cloud respond to CVE-2026-0004 across many processor families
AMD published firmware guidance for CVE-2026-0004, a transient execution flaw that may let local code infer data in the L1D cache. Google Cloud lists affected machine series and requires a guest patch plus a stop and start.
On this page
What changed
AMD has published security bulletins AMD-SB-3055 and AMD-SB-4018 for CVE-2026-0004, a transient execution vulnerability in some AMD processors that may let an attacker with code execution infer data in the L1D cache and potentially leak sensitive information across privileged boundaries. The CVE (Common Vulnerabilities and Exposures) record was published on November 12, 2026, and carries a CVSS (Common Vulnerability Scoring System) 4.0 base score of 5.7, rated Medium by AMD. According to The Hacker News, the Xen Project calls the flaw TSA-Fill, and Google rates the issue Medium.
Which systems are affected
AMD’s advisory marks a broad set of processor families as affected by default and lists specific firmware versions as unaffected, including EPYC 9005 and 8005 series with TurinPI_1.0.0.B, Ryzen 9000HX with FireRangeFL1 PI-1.0.0.0i, and Ryzen AI 300 with StrixKrackanPI-FP8_1.1.0.0h and StrixKrackanPI-FP8_1.1.0.2g. Ryzen 9000 desktop processors list ComboAM5PI_1.3.0.1d as unaffected, and Threadripper 7000 and 9000 processors list ShimadaPeakPI-SP6-1.0.0.1h. The report lists the affected Google Cloud machine series as C4D, N4D, H4D, Z4D, and G4, including bare-metal instances of C4D and Z4D.
Why it matters
CVE-2026-0004 is a local attack with high attack complexity that requires low privileges and no user interaction. The report says Google Cloud VMs on AMD Turin chips need a guest OS patch and a stop-and-start to protect against three CPU side-channel flaws. The report says neither AMD nor Google reports any exploitation of the flaws in its bulletins.
What to do
Apply both the platform firmware and the OS updates that AMD says are needed to fully mitigate the flaws on Turin servers. The report notes that rebooting the guest OS is not enough: after the CPU information update reaches a VM, stop and start it. Debian has fixed CVE-2026-0004 in its Linux kernel only in its unstable branch, and the Xen Project has published hypervisor patches in its Xen advisory. The report adds that microcode for all TSA flaws on Zen 5 has been in linux-firmware since September 23.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .