GCP-2026-081 — Published: 2026-11-10Description Description Severity Notes AMD has disclosed three vulnerabilities that affect 5th generation AMD EPYC…

Published: 2026-11-10Description Description Severity Notes AMD has disclosed three vulnerabilities that affect 5th generation AMD EPYC processors (code-named Turin): CVE-2024-36350 and CVE-2024-36357, which AMD previously disclosed for earlier EPYC processors, and a new vulnerability, CVE-2026-0004. Under certain conditions, an attacker could infer data from the store queue or the L1 data cache, potentially leaking sensitive information across privilege boundaries. Affected Compute Engine machine series: C4D, N4D, H4D, Z4D, and G4, including C4D and Z4D bare metal instances. Google has applied mitigations that protect against attacks between VMs and between VMs and the host. To protect against attacks inside a VM, such as between processes, you need to update your guest operating system. What should I do? VMs: Update your guest operating system when your OS vendor releases fixes. Starting November 10th, Google will update the CPU information that VMs report so that patched guest kernels can turn on their mitigations. After the update reaches your VM, stop and start the VM. Rebooting the guest OS isn't enough. Bare metal and nested virtualization: If you run your own OS or hypervisor on a bare metal instance, apply your vendor's fixes when they're available. If you run a hypervisor inside a VM, Google will update the CPU information that VMs report so that patched guest kernels can turn on their mitigations. After the update reaches your VM, stop and start the VM. Rebooting the guest OS isn't enough. GKE: Updated GKE node images for Turin-based bare metal instances will be made available. Upgrading your nodes picks up the CPU information update. This bulletin will be updated once the new node image is available. Cloud Run: No action is required. For more information, see AMD security bulletins AMD-SB-7073 and AMD-SB-3055. What vulnerabilities are being addressed? CVE-2024-36350 (TSA-SQ): may allow an attacker to infer data from previous stores, potentially leaking sensitive information. CVE-2024-36357 (TSA-L1): may allow an attacker to infer data in the L1 data cache, potentially leaking sensitive information across privilege boundaries. CVE-2026-0004: may allow an attacker to infer data in the L1 data cache, potentially leaking sensitive information across privilege boundaries. These are Transient Scheduler Attacks (TSA), a type of side-channel vulnerability. Under certain conditions, the processor can briefly use data before confirming it's valid. An attacker running code on the same processor core may be able to measure the resulting timing differences to infer data from another process, the kernel, another VM, or the host. Medium CVE-2024-36350 CVE-2024-36357 CVE-2026-0004