Google Cloud Warns Three AMD Turin CPU Flaws Could Leak Data Across Processes in VMs

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. The company 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. The affected

Data Breach Cloud Computing Operating Systems Hardware & Chips
Read the full article at The Hacker News Removal request

This page shows only the headline and the short summary. The full text is published by the original source.

Related news

Full archive →
CyberInsider

Apple isolates HomeView camera and mic data with Secure Exclaves

Apple has shared more details on a security architecture called Secure Exclaves that keeps raw camera and microphone data used by HomeView’s background sensing isolated from the main operating system. The design also requires a visible privacy indicator before full audio or video can be handed over to the system during an active session. Apple … The post Apple isolates HomeView camera and mic data with Secure Exclave…

CSO Online

AI found Linux kernel bugs that remained undetected for decades

A Microsoft research project combining AI agents with human security researchers uncovered 59 Linux kernel vulnerabilities, including bugs that had survived in production code for more than 20 years. While AI dramatically accelerated the discovery process, the researchers found that validating flaws, developing patches, and working with maintainers remained overwhelmingly human-intensive. The research, conducted by M…

The Hacker News

Webinar: See How Identity Blind Spots Put Your SOC at Risk and How to Close Them

Security teams have more alerts, logs, and monitoring tools than ever. Yet when an attack happens, one simple question can still take too long to answer: Who or what is behind this activity, and what can they access? A suspicious login might belong to an employee. An unusual API call could come from a machine account. Or an AI agent might be accessing sensitive systems using permissions nobody