AMD Turin TSA flaws: The Hacker News reports Google Cloud VM warning
The Hacker News reports Google Cloud says three AMD Turin CPU flaws affect some VMs; install OS fixes, then stop and start the VM.
- Published
- Ecosystem
- CloudCritical infrastructure
- Fixed in
- Linux kernel commit for TSA on Zen 5 in the kernel source tree, Debian unstable kernel fix for CVE-2026-0004, microcode in linux-firmware since September 23, Xen hypervisor patches; Google Cloud OS vendor fixes and GKE node images not yet confirmed
- Exploitation
- No. According to The Hacker News, none of the three is in CISA’s KEV catalog and neither Google nor AMD reports exploitation in its bulletins.
Live scores
CVE-2024-36350- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.670
likely exploited - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2024-36357- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.395
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-0004- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.045
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
What happened
According to The Hacker News, Google said this week that Google Cloud VMs on AMD Turin chips need a guest OS patch and a stop-and-start to protect against three CPU side-channel flaws. The Hacker News reports that Google has already applied mitigations against attacks between VMs, and between VMs and the host. Inside a VM, the flaws may let an attacker with code on the same processor core infer data from other processes or the kernel, according to the same report.
The Hacker News says all three are Transient Scheduler Attacks (TSA). Two of them, TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357), were first disclosed on July 8, 2025, for earlier EPYC processors. The report says AMD now states that its Zen 5 processors, which include Turin, are “impacted differently from previously characterized AMD processors.” The third flaw, CVE-2026-0004, is new and, per the report, may let an attacker who can run code on a system infer data in the processor’s L1 data cache.
The Hacker News reports that the Xen Project calls the new flaw TSA-Fill and says an earlier statement has been corrected: “AMD had previously said that Zen5 CPUs were not vulnerable to TSA-SQ and TSA-L1.”
Per The Hacker News, Google rates the issue Medium, and AMD classifies all three as local attacks with high attack complexity that need only low privileges. The outlet states that none of the three is in CISA’s KEV catalog and that neither company reports exploitation. We have only this one outlet’s account; we did not review the Google, AMD or Xen bulletins directly.
Am I affected?
According to The Hacker News, the affected Google Cloud machine series are C4D, N4D, H4D, Z4D and G4, including bare-metal instances of C4D and Z4D. The outlet says Turin is the code name for fifth-generation AMD EPYC processors, so Turin servers on your own hardware are also in scope; AMD says both platform firmware and OS updates are needed for a full mitigation.
Per the same report, Google’s guidance by service is:
- VMs: install your OS vendor’s fix when it ships.
- Bare metal (C4D, Z4D): if you run your own OS or hypervisor, apply your vendor’s fixes when available.
- Hypervisors inside a VM: the same CPU information update applies.
- GKE: updated node images for Turin-based bare metal are planned, but the bulletin does not yet list them as available, according to the report.
- Cloud Run: no action needed.
The Hacker News says customers on older Rome, Milan and Genoa processors received the same stop-and-start instruction in an earlier bulletin on July 8, 2025.
Not confirmed in the source: what to do in the meantime for VMs whose OS vendor has not shipped a fix, and how to tell when the CPU information update has reached a VM.
What to do now
- Check whether you run C4D, N4D, H4D, Z4D or G4 instances, or your own Turin hardware. The Hacker News reports these are the affected platforms.
- Install your OS vendor’s kernel update when it ships. The Hacker News reports that a Linux kernel commit mitigating TSA on Zen 5 is in the kernel source tree, and that Debian has fixed CVE-2026-0004 only in its unstable branch, with bookworm, trixie and forky still listed as vulnerable in its tracker.
- After Google’s CPU information update reaches the VM, stop and start it. Per Google, as quoted by The Hacker News: “Rebooting the guest OS isn’t enough.”
- On GKE, watch for the updated node images for Turin-based bare metal and upgrade nodes once they are listed, per the report.
- On your own Turin servers, apply platform firmware and OS updates. AMD says the mitigation may affect performance, so weigh the risk for your workloads, according to The Hacker News. The report adds that Xen Project has published hypervisor patches and that microcode for all TSA flaws on Zen 5 has been in linux-firmware since September 23.