
TSA-Fill (CVE-2026-0004). This is a newly identified flaw that allows an attacker with local code execution to infer data stored in the processor's L1 data cache. The warning applies to VMs running on the C4D, N4D, H4D, Z4D, and G4 machine series.
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
A transient execution vulnerability in some AMD processors may allow an attacker with the ability to execute code on the system to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE

TSA-Fill (CVE-2026-0004). This is a newly identified flaw that allows an attacker with local code execution to infer data stored in the processor's L1 data cache. The warning applies to VMs running on the C4D, N4D, H4D, Z4D, and G4 machine series.

Google Cloud bulletin GCP-2026-081 covers three Transient Scheduler Attacks flaws in 5th-generation AMD EPYC Turin processors. Google has protected the host; customers must update their guest operating systems. ✍️ https://geopolitiki.com/technology/amd-epyc-turin-three-transient-scheduler-attacks-vulnerabilities-zen-5-google-cloud-gcp-2026-081-cve-2026-0004-cve-2024-36350-cve-2024-36357/

Google Cloud says VMs on AMD EPYC Turin (5th-gen EPYC server CPUs) need an OS patch and a stop-start, not a reboot, to enable mitigations for CVE-2026-0004, a new Zen 5 side channel leaking L1 data between processes. https://docs.cloud.google.com/support/bulletins#gcp-2026-081
Post summary
Google Cloud advisory stating that VMs on AMD EPYC Turin require an OS patch plus a stop-start (not reboot) to enable mitigations for CVE-2026-0004, a Zen 5 side-channel vulnerability leaking L1 data between processes. The named remediation action makes Patch the primary classification.

Researchers observed that CVE-2026-0004 (TSA-Fill) requires only low-privilege code execution on a shared vCPU — no network exploit needed — to infer kernel memory and process data across privilege boundaries on AMD Turin-based Google Cloud VMs. Many guest OS distributions have not yet shipped stable patches, leaving intra-VM exploitation paths open even on mitigated platforms. Runtime segmentation enforcing least-privilege workload identity can help restrict lateral movement if kernel material is leaked. #CloudSecurity #ZeroTrust 🔗 Full TRC analysis: https://aviatrix.ai/threat-research-center/google-cloud-amd-turin-cpu-tsa-cve-2026-0004-vm-side-channel

Google Cloud is warning about three Transient Scheduler Attacks on AMD Turin and Zen 5 — TSA-SQ, TSA-L1, and a new TSA-Fill, CVE-2026-0004 — that can leak data across processes in VMs. The fix is a guest OS patch plus a stop-and-start. The side channel crosses the VM boundary, which is the boundary the whole cloud model rests on. The patch is the easy part. The restart is the part that takes the scheduling. The VM boundary is the promise. The side channel is the exception. https://thehackernews.com/2026/11/google-cloud-warns-three-amd-turin-cpu.html