Google Cloud Issues Mitigation Guidance for AMD Turin VMs Following CPU Side-Channel Flaws

Cloud computing customers utilizing Google Cloud Virtual Machines (VMs) powered by AMD’s Turin processors are being urged to implement guest operating system patches and execute a critical stop-and-start sequence for their instances. The mandate comes as part of a coordinated security response to three CPU side-channel vulnerabilities impacting modern AMD EPYC hardware. While Google has successfully deployed mitigations at the infrastructure level to prevent cross-VM and VM-to-host attacks, additional steps are required to secure workloads from threats originating within the same processor core.

According to technical advisories released this week, the affected Google Cloud machine series include the C4D, N4D, H4D, Z4D, and G4 configurations, alongside bare-metal instances of the C4D and Z4D families. The underlying hardware at the center of the advisory—code-named Turin—represents AMD’s fifth-generation EPYC processor lineup, built on the advanced Zen 5 architecture.

The security concern revolves around a class of vulnerabilities known as Transient Scheduler Attacks (TSA). Two of the three flaws, designated as TSA-SQ (tracked as CVE-2024-36350) and TSA-L1 (tracked as CVE-2024-36357), were initially disclosed on July 8, 2025, during an evaluation of earlier-generation AMD EPYC processors. At the time of that initial disclosure, hardware manufacturers and software maintainers believed the impact was restricted to previous architectures.

However, recent analysis by AMD has revealed that Zen 5 processors are impacted differently than their predecessors. This reassessment is accompanied by the disclosure of a brand-new vulnerability cataloged as CVE-2026-0004. This third flaw could potentially allow an unauthorized actor capable of executing local code on a targeted system to infer sensitive data residing within the processor’s L1 data cache.

The Xen Project, which maintains the widely utilized Xen hypervisor, has formally recognized the new vulnerability under the identifier TSA-Fill. In its technical communications, the organization clarified that previous assumptions regarding Zen 5 hardware safety required correction, noting that AMD had previously stated that Zen 5 CPUs were not vulnerable to the TSA-SQ and TSA-L1 variants.

Google Cloud Warns Three AMD Turin CPU Flaws Could Leak Data Across Processes in VMs

Despite the technical complexity of the underlying mechanisms, major stakeholders have generally rated the overall severity of the threat with moderate urgency. Google has classified the issue as having a Medium severity level. Similarly, AMD’s official Zen 5 security bulletin and the specialized CVE-2026-0004 advisory categorize all three vulnerabilities as local attacks requiring low user privileges, though they note that the inherent attack complexity is relatively high.

As of publication, none of the three newly addressed vulnerabilities have been added to the Known Exploited Vulnerabilities (KEV) catalog maintained by the U.S. Cybersecurity and Infrastructure Security Agency (CISA). Furthermore, neither Google nor AMD has received or reported any evidence of active, in-the-wild exploitation targeting these specific CPU flaws.

What Google Cloud Customers Need to Do

Cloud administrators maintaining workloads on the impacted Google Cloud instances must navigate a specific recovery path to ensure their environments are fully protected. Google’s published security documentation outlines the necessary operational procedures, which closely mirror the mitigation protocols previously deployed for older processor generations.

Customers operating on earlier AMD processor architectures—such as Rome, Milan, and Genoa—were subjected to the same stop-and-start mandate when the original transient scheduler vulnerabilities were disclosed in July 2025. For the current Zen 5 hardware, Google’s guidance requires administrators to apply updated guest operating system patches followed by a complete stop and subsequent restart of the affected virtual machine instances to ensure the newly minted CPU microcode and scheduler logic are properly loaded by the kernel.

Google has indicated that no immediate action is required for virtual machines where the respective guest operating system vendor has not yet released a verified software fix. However, the cloud provider’s documentation currently lacks explicit instructions on how administrators can programmatically verify whether the updated CPU information and mitigation patches have successfully propagated to a running virtual machine instance.

Google Cloud Warns Three AMD Turin CPU Flaws Could Leak Data Across Processes in VMs

Broader Ecosystem and Firmware Updates

Beyond the cloud environment, the broader enterprise ecosystem is moving to incorporate the necessary software safeguards. A kernel commit designed to mitigate Transient Scheduler Attacks on Zen 5 architecture, including the newly introduced variant, has been integrated into the upstream Linux kernel source tree.

Adoption across downstream Linux distributions varies. For instance, the Debian project has addressed CVE-2026-0004 within the Linux kernel of its unstable branch. However, Debian’s official security tracker indicates that stable and testing distributions, including bookworm, trixie, and forky, continue to list the relevant kernels as vulnerable while maintainers backport the necessary patches.

For organizations managing physical Turin servers on-premises, AMD emphasizes that comprehensive protection requires a combination of updated platform firmware and operating system patches. Because these hardware-level security mitigations can introduce performance overhead, system administrators are advised to carefully evaluate the operational risks to their specific enterprise workloads before rolling out updates across production environments.

Hypervisor maintainers have also taken swift action. The Xen Project has published hypervisor-specific patches via its official advisory channels, noting that the requisite microcode packages addressing all TSA flaws on Zen 5 processors have been available within the standard linux-firmware repositories since late September.