← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Google Cloud warns of three AMD Turin CPU flaws affecting VMs, requiring guest OS patches

🔄 Updated 9d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Three TSA flaws affect AMD Turin CPUs in Google Cloud VMs.
  • Flaws allow data inference between processes or kernel within a VM.
  • Guest OS patches and VM stop-and-start are required for mitigation.
  • Google Cloud applied mitigations for inter-VM and VM-host attacks.

AMD Turin CPU Flaws Disclosed

Google Cloud announced that three Transient Scheduler Attack (TSA) flaws affect AMD Turin CPUs used in its virtual machines. These vulnerabilities could allow an attacker with code running on the same processor core to infer data from other processes or the kernel within a VM. The affected machine series include C4D, N4D, H4D, Z4D, and G4, as well as bare-metal instances of C4D and Z4D. Turin is the codename for fifth-generation AMD EPYC processors.

Details of the Vulnerabilities

Two of the flaws, TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357), were previously disclosed for earlier EPYC processors. AMD now states that its Zen 5 processors, including Turin, are impacted differently. A third, new flaw, CVE-2026-0004 (named TSA-Fill by the Xen Project), allows an attacker to infer data in the processor's L1 data cache. AMD classifies all three as local attacks with high attack complexity requiring low privileges. Neither Google nor AMD has reported any exploitation of these flaws.

Mitigation Steps for Google Cloud Customers

Google Cloud customers operating VMs on AMD Turin chips must install their OS vendor's fix when available. Google Cloud will update the CPU information reported by VMs, enabling patched guest kernels to activate mitigations. After this update reaches a VM, a stop-and-start operation is necessary; a simple guest OS reboot is insufficient. For bare metal instances, customers must apply vendor fixes for their OS or hypervisor. GKE users will receive updated node images for Turin-based bare metal instances, and upgrading nodes will incorporate the CPU information update.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Google Cloud has identified three Transient Scheduler Attack (TSA) flaws in AMD Turin CPUs used in its VMs, which could allow data leakage between processes within a VM. Customers need to apply guest OS patches and perform a stop-and-start operation on affected VMs to enable mitigations. Google Cloud has already implemented mitigations against attacks between VMs and between VMs and the host.