Executive Summary

In November 2026, Google Cloud disclosed three hardware-level side-channel vulnerabilities affecting AMD Turin (5th-gen EPYC / Zen 5) processors used in its C4D, N4D, H4D, Z4D, and G4 machine series, including bare-metal instances. Classified as Transient Scheduler Attacks (TSA), two flaws—TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357)—were previously thought not to affect Zen 5; AMD has since corrected that position. A third, newly identified variant, CVE-2026-0004 (TSA-Fill), allows an attacker with low-privilege code execution on the same physical core to infer data from the L1 data cache across process or kernel boundaries. Google has mitigated inter-VM and VM-to-host attack paths at the platform level, but intra-VM exploitation requires both a stop-and-start lifecycle event and a patched guest OS kernel, which many distributions have not yet shipped to stable branches.

This disclosure underscores a broadening attack surface at the hardware abstraction layer in multi-tenant cloud environments. As workloads grow denser on shared silicon—particularly AI and confidential-compute workloads on high-core-count EPYC platforms—CPU microarchitectural vulnerabilities represent an escalating risk that neither network controls nor application-layer security alone can fully address.

Why This Matters Now

Multi-tenant cloud adoption is accelerating, and AMD EPYC Turin processors underpin a growing share of high-performance and AI workloads on Google Cloud. With CVE-2026-0004 unpatched in most stable Linux distributions and a stop-and-start lifecycle requirement that many production teams defer, the intra-VM attack surface remains open today—making timely patching and workload isolation controls immediately critical for regulated and data-sensitive industries.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

Customers must install their OS vendor's kernel patch for CVE-2026-0004, TSA-SQ, and TSA-L1 when available, then perform a full stop-and-start of each affected VM—a reboot alone is insufficient. Bare-metal C4D and Z4D instance operators must also apply platform firmware updates from AMD.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant because the attacker's progression from a low-privilege VM foothold toward lateral movement, credential abuse, and exfiltration depends on the absence of workload-level segmentation and controlled egress paths. By enforcing identity-aware segmentation and east-west traffic policy, CNSF would likely constrain how far extracted credentials and inferred memory contents could be operationalized across the environment.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Consistent Zero Trust policy applied at the workload boundary would likely reduce the reachability of this initial foothold to other workloads and services within the environment, constraining how broadly the compromised execution context can be observed or leveraged even before privilege escalation begins.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Even where kernel memory leakage occurs at the CPU level, Zero Trust segmentation enforcing least-privilege identity-based policy at the workload layer would likely reduce the blast radius by limiting which resources and identities the extracted credentials could actually reach and act upon.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic controls enforcing segmentation between workloads and service identities would likely detect and constrain unauthorized lateral service-to-service connections arising from compromised credential use, reducing the attacker's ability to pivot freely across workloads even with valid-looking credentials.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Centralized traffic observability across cloud-native flows would likely surface anomalous outbound connection patterns from affected VM instances, reducing the attacker's ability to maintain a durable, undetected command and control channel by flagging unusual egress behavior for investigation.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement with FQDN filtering would likely constrain the attacker's ability to transfer staged data to unrecognized external destinations, reducing the probability of successful exfiltration by limiting permitted outbound paths to explicitly approved endpoints.

Impact (Mitigations)

The residual impact would likely be constrained to the scope of the initially compromised workload, with reduced ability to monetize leaked memory contents broadly across the environment, though cryptographic material and session tokens inferred within the VM itself may still represent meaningful exposure for that specific workload's data.

Impact at a Glance

Affected Business Functions

  • Cloud Virtual Machine Workload Isolation
  • Multi-Tenant Data Confidentiality
  • Bare-Metal and Hypervisor Security
  • Google Kubernetes Engine (GKE) Node Integrity
Operational Disruption

Estimated downtime: 1 days

Financial Impact

Estimated loss: N/A

Data Exposure

Process-level memory data and kernel memory contents may be inferred by a co-located attacker on the same physical CPU core within a VM. In multi-tenant cloud environments running AMD Turin (Zen 5) processors, sensitive workload data such as cryptographic keys, session tokens, authentication credentials, or confidential application memory could be speculatively leaked across process boundaries. Affected Google Cloud machine series include C4D, N4D, H4D, Z4D, and G4, including bare-metal variants. No confirmed data exfiltration events have been reported; risk is theoretical but credible in shared-core cloud scenarios.

Recommended Actions

  • • Apply guest OS vendor patches for CVE-2024-36350, CVE-2024-36357, and CVE-2026-0004 immediately upon availability, then perform a full stop-and-start (not just reboot) of all affected Turin-based VMs (C4D, N4D, H4D, Z4D, G4) to activate CPU microcode mitigations — a reboot alone is insufficient per Google's bulletin.
  • • Enforce Zero Trust Segmentation with identity-based microsegmentation policies between all workloads on affected VM series to constrain lateral movement even if an attacker achieves local code execution and leaks credential material via the side-channel.
  • • Deploy East-West Traffic Security controls to monitor and enforce workload-to-workload and service-to-service communication policies within VPCs hosting Turin-based instances, detecting anomalous lateral connections that may indicate use of side-channel-harvested credentials.
  • • Enable Egress Security and Policy Enforcement with FQDN filtering and data-loss prevention on all outbound paths from affected VM instances to block unauthorized exfiltration of data inferred through the CPU side-channel, and activate Inline IPS (Suricata) rules to detect known memory-scraping and side-channel exploit tooling signatures.
  • • Leverage Multicloud Visibility and Control to establish behavioral baselines for all workloads on affected machine series and configure alerting for anomalous outbound connection patterns, privilege escalation API calls, or unexpected cross-workload traffic flows that may indicate active exploitation of these CPU flaws.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image