• Sources: discussion
  • Summary: AMD now says Zen 5 is affected by TSA-SQ (CVE-2024-36350) and TSA-L1 (CVE-2024-36357), reversing an earlier statement, and adds a new variant, CVE-2026-0004, which Xen calls TSA-Fill. Google has mitigated cross-VM and VM-to-host attacks, but inside a guest a process on the same core may infer data from other processes or the kernel until the guest kernel is patched and the VM is stopped and started after Google updates its reported CPU information. The Linux kernel has a mitigation commit, Debian has fixed only unstable so far, and Zen 5 microcode has been in linux-firmware since 2026-09-23.
  • Why it matters: Anyone running fifth-generation EPYC hosts or VMs must track both microcode and kernel updates, because a guest reboot alone does not enable the mitigation on Google Cloud.
  • Background: Transient Scheduler Attacks are AMD side channels disclosed on 2025-07-08, in which the timing of instructions under certain microarchitectural conditions reveals data from the store queue or L1 data cache. Like earlier Spectre-class flaws, they need code running on the same core, so cloud providers isolate tenants at the hypervisor while guests must protect their own processes. A guest kernel only enables a mitigation when the CPU it sees reports the matching feature bits, which is why Google must update the CPU information first.
  • Follow-up: Turin GKE node images, Debian stable kernel fixes, and firmware from other cloud and server vendors.