Google Details Three AMD Turin CPU Flaws and Required VM Updates

Summary
Google says three AMD Zen 5/Turin transient-scheduler flaws could expose data within a VM. Google Cloud customers need a guest OS fix and VM stop/start; no exploitation is reported, and bare-metal systems need firmware and OS updates.
Key points
- The three transient scheduler flaws are TSA-SQ (CVE-2024-36350), TSA-L1 (CVE-2024-36357), and the newly disclosed TSA-Fill (CVE-2026-0004).
- Code running on the same processor core may infer data from other processes or the kernel inside a VM; TSA-Fill may expose data in the processor's L1 data cache.
- Affected Google Cloud series include C4D, N4D, H4D, Z4D, and G4; bare-metal C4D and Z4D instances are also affected.
- Google says it has mitigated attacks between VMs and between VMs and the host. Customers need a guest OS patch and must stop and start the VM.
- The article says none of the flaws is listed in CISA's KEV catalog, and the companies report no exploitation.
- A Zen 5 mitigation is in the Linux kernel source tree; Debian's fix for CVE-2026-0004 is in unstable, while the article says several other Debian branches remain vulnerable.
- AMD says Turin systems on customers' own hardware need platform firmware and OS updates; mitigation may affect performance. Xen has published patches, and microcode is available in linux-firmware.
Article Details
- Vulnerability Types
- Transient Scheduler Attacks (CPU side-channel flaws)
- Severity
- Medium (Google rating)
- Affected Versions
- AMD EPYC Zen 5 (Turin)
- Exploitation Status
- not_reported
- Exploit Availability
- unknown
- Patch Status
- partial
- Workarounds
- For affected Google Cloud VMs, apply the guest OS patch and stop and start the VM.
CVE
CVE-2024-36350AMD · AMD EPYC™ 7003 Series Processors; AMD · AMD EPYC™ 8004 Series Processors; +21 moreAll three flaws are Transient Scheduler Attacks (TSA). Two of them, TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357), were first disclosed on July 8, 2025, for earlier EPYC processors.CVE-2024-36357AMD · AMD EPYC™ 7003 Series Processors; AMD · AMD EPYC™ 8004 Series Processors; +21 moreAll three flaws are Transient Scheduler Attacks (TSA). Two of them, TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357), were first disclosed on July 8, 2025, for earlier EPYC processors.CVE-2026-0004Vendor / Product unavailableTurin, are "impacted differently from previously characterized AMD processors." The third flaw, CVE-2026-0004, is new. It may let an attacker who can run code on a system infer data in the processor's L1 data
Vendors
AMDGoogle Cloud VMs on AMD Turin chips need a guest OS patch and a stop-and-start to protect against three CPU side-channel flaws, Google said this week.Debianthat mitigates TSA on Zen 5, including the new variant, is in the Linux kernel source tree. As of today, Debian has fixed CVE-2026-0004 in its Linux kernel only in its unstable branch. Its security tracker still listsGoogle CloudGoogle Cloud VMs on AMD Turin chips need a guest OS patch and a stop-and-start to protect against three CPU side-channel flaws, Google said this week.Xen ProjectThe Xen Project, which maintains the Xen hypervisor, calls the new flaw TSA-Fill. It also says an earlier statement has been corrected: "AMD had previously said that Zen5 CPUs were not vulnerable to TSA-SQ and TSA-L1."
Products
AMD EPYCThe affected machine series are C4D, N4D, H4D, Z4D,, and G4, including bare-metal instances of C4D and Z4D. Turin is the code name for fifth-generation AMD EPYC processors.Google Cloud VMsGoogle Cloud VMs on AMD Turin chips need a guest OS patch and a stop-and-start to protect against three CPU side-channel flaws, Google said this week.Linux kernelA kernel commit that mitigates TSA on Zen 5, including the new variant, is in the Linux kernel source tree. As of today, Debian has fixed CVE-2026-0004 in its Linux kernel only in its unstable branch. Its securityXenThe Xen Project, which maintains the Xen hypervisor, calls the new flaw TSA-Fill. It also says an earlier statement has been corrected: "AMD had previously said that Zen5 CPUs were not vulnerable to TSA-SQ and TSA-L1."
