Early warning
Google Cloud warns three AMD Turin CPU flaws could leak data across VMs
Google Cloud said three AMD Turin CPU side-channel flaws, all Transient Scheduler Attacks, could let an attacker with code on the same core infer data from other processes or the kernel inside a VM.
Written by a model from the sources below. Verify against them.
- Kind
- Pending CVE
- Vendor
- AMD
- Product
- EPYC Turin (Zen 5) processors
- Status
- Confirmed
- First seen
- Confirmed
Summary
Google Cloud said three AMD Turin CPU side-channel flaws, all Transient Scheduler Attacks, could let an attacker with code on the same core infer data from other processes or the kernel inside a VM. Google has applied mitigations against attacks between VMs and between VMs and the host, while customers need a guest OS patch and a stop-and-start; no exploitation has been reported by Google or AMD.
What to do
Install your OS vendor's kernel fix for the Turin CPU flaws when it ships.
Stop and start VMs after the CPU information update reaches them, since a guest reboot is not enough.
On your own Turin servers, apply both platform firmware and OS updates.
Timeline
- Made public by The Hacker News
- First seen by cve.now
- Confirmed as CVE-2024-36350
Evidence 1
- PressThe Hacker News
“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, Google said this week.”
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about SZB-34b40f857b
Has AMD confirmed it?
Yes. Confirmed as CVE-2024-36350.Source: The Hacker News
What should AMD and EPYC Turin users do?
Install your OS vendor's kernel fix for the Turin CPU flaws when it ships. Stop and start VMs after the CPU information update reaches them, since a guest reboot is not enough. On your own Turin servers, apply both platform firmware and OS updates.
Does it have a CVE?
Yes. It is tracked as CVE-2024-36350, CVE-2024-36357 and CVE-2026-0004.Source: CVE-2024-36350, CVE-2024-36357, CVE-2026-0004