Google Details Three AMD Turin CPU Flaws and Required VM Updates

· Original article ↗

Summary

Google says three AMD Zen 5/Turin transient-scheduler flaws could expose data within a VM. Google Cloud customers need a guest OS fix and VM stop/start; no exploitation is reported, and bare-metal systems need firmware and OS updates.

Key points

  • The three transient scheduler flaws are TSA-SQ (CVE-2024-36350), TSA-L1 (CVE-2024-36357), and the newly disclosed TSA-Fill (CVE-2026-0004).
  • Code running on the same processor core may infer data from other processes or the kernel inside a VM; TSA-Fill may expose data in the processor's L1 data cache.
  • Affected Google Cloud series include C4D, N4D, H4D, Z4D, and G4; bare-metal C4D and Z4D instances are also affected.
  • Google says it has mitigated attacks between VMs and between VMs and the host. Customers need a guest OS patch and must stop and start the VM.
  • The article says none of the flaws is listed in CISA's KEV catalog, and the companies report no exploitation.
  • A Zen 5 mitigation is in the Linux kernel source tree; Debian's fix for CVE-2026-0004 is in unstable, while the article says several other Debian branches remain vulnerable.
  • AMD says Turin systems on customers' own hardware need platform firmware and OS updates; mitigation may affect performance. Xen has published patches, and microcode is available in linux-firmware.

Article Details

Vulnerability Types
  • Transient Scheduler Attacks (CPU side-channel flaws)
Severity
Medium (Google rating)
Affected Versions
  • AMD EPYC Zen 5 (Turin)
Exploitation Status
not_reported
Exploit Availability
unknown
Patch Status
partial
Workarounds
  • For affected Google Cloud VMs, apply the guest OS patch and stop and start the VM.

CVE

Vendors

Products

Related Articles