// Security Advisory Triage
AMD EPYC Turin CPUs vulnerable to three side-channel attacks across VM boundaries
Google Cloud security bulletins · published 2026-11-13 19:46 UTC
WHAT CHANGEDGoogle disclosed GCP-2026-081 on 10 November 2026, covering CVE-2024-36350, CVE-2024-36357, and CVE-2026-0004 affecting 5th generation AMD EPYC (Turin) processors. The vulnerabilities allow attackers to infer data from the store queue or L1 data cache across privilege boundaries, including between VMs and between processes within a VM. Affected Compute Engine machine series: C4D, N4D, H4D, Z4D, and G4, including C4D and Z4D bare metal instances. Google applied mitigations protecting between VMs and between VMs and the host; guest OS updates are required for in-VM protection.
WHY IT MATTERSAn attacker with code execution on an affected processor core can measure timing differences to infer sensitive data from another process, the kernel, another VM, or the host. Google's mitigations do not protect against attacks between processes inside a VM — those require a patched guest OS and a stop/start cycle to pick up updated CPU information that enables kernel mitigations.
WHAT TO DOFor VMs: update guest OS when vendor releases fixes, then stop and start the VM after Google's CPU information update reaches it (starting 10 November 2026); reboot alone is insufficient. For bare metal: apply vendor fixes when available, then stop and start. For GKE on Turin bare metal: upgrade nodes when updated node images become available (bulletin will be updated with availability). Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-081 and AMD-SB-7073, AMD-SB-3055.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-081 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-081 +2026-11-10T01:46:31.757411+00:00 + +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
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | New AMD EPYC vulnerability affecting GCP managed compute with required guest OS and infrastructure updates. |
| signals | affects cloud control plane infrastructure (Compute Engine, GKE, Cloud Run) · customer cannot patch — requires Google CPU microcode update + guest OS update · new CVE (CVE-2026-0004) disclosed alongside two prior CVEs · side-channel vulnerability affecting data isolation across VMs and privilege boundaries · actionable remediation required: stop/start VMs, upgrade GKE nodes, update guest OS · specific affected machine series listed (C4D, N4D, H4D, Z4D, G4) · published date with immediate mitigation timeline (November 10th CPU info update) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |