AEGLIX News
Google Cloud has warned that virtual machines running on AMD Turin processors require a guest operating system patch and a full stop-and-start cycle to protect against three CPU side-channel vulnerabilities, according to a notice from the cloud provider. The company rates the overall issue as Medium severity and says it has already applied mitigations to block attacks between virtual machines and between VMs and the host infrastructure. However, inside a VM, the flaws may allow an attacker with code execution on the same processor core to infer data from other processes or the kernel.
Google Cloud's advisory covers machine series C4D, N4D, H4D, Z4D, and G4, with bare-metal instances of C4D and Z4D also included. Turin serves as the code name for fifth-generation AMD EPYC processors. Each of the three vulnerabilities falls under the Transient Scheduler Attacks (TSA) classification, a group of side-channel flaws that leverage CPU scheduling behavior to leak data across security boundaries.
TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357) were initially disclosed on July 8, 2025, affecting earlier EPYC processor generations. The third vulnerability, CVE-2026-0004, is newly identified and could allow an attacker with code execution on a system to infer data residing in the processor's L1 data cache. The Xen Project refers to this new flaw as TSA-Fill.
Google has already deployed mitigations at the infrastructure level to prevent cross-VM and VM-to-host exploitation. To address the remaining intra-VM risk, customers must apply a guest OS patch provided by their operating system vendor and then perform a complete stop-and-start of the affected VM instances; a simple reboot is insufficient. The requirement applies to all listed machine series running on AMD Turin hardware.
Report prepared 2026-11-12 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.