One email a day: the top topics, each with the angle and the story, before you plan content. The daily report isn't open yet — leave your email and we'll tell you when it opens.
Cooling
KVM guest-to-host escape breaks VM isolation on AMD hosts
Heat 38 · #22 in Security · Cooling2 reports · 2 sources · First reported Nov 18 · Updated Nov 20
The story
Terra Security has disclosed a guest-to-host escape in KVM, the Linux kernel's hypervisor, affecting hosts with AMD CPUs. The flaw is a use-after-free in nested virtualization that lets a guest virtual machine reach into host memory: the researchers demonstrated it on a DigitalOcean droplet by reading about 127 GB of host RAM, and showed an arbitrary write — 32 chosen bytes into a live host kernel page — on their own bare-metal AMD server. The bug sat in the kernel for just under four years and was introduced by the fix for an earlier flaw, CVE-2022-3344. Terra reported it to the KVM maintainers on October 21, 2026; a fix was merged on November 2 and shipped in stable kernel 7.3.5 and the LTS releases 6.18.64 and 6.12.118 on November 17. Until hosts update, the suggested mitigation is to disable nested virtualization by setting kvm_amd nested=0.
Latest development
revived in round 195, still active this round
How it unfolded
revived in round 195, still active this round
cooling cleared, status active (round 35 revival precedent)
back in HN top 30 after cooling in round 190
no Lobsters/YouTube/Techmeme keepalive this round
a LowEndTalk thread reposts the finding (forum, not counted as a second platform)
mitigation is updating the kernel or setting kvm_amd nested=0
Oct 21
reported to KVM maintainers 2026-10-21, fix merged 2026-11-02, tagged v7.4-rc2 2026-11-09, released in stable 7.3.5 and LTS 6.18.64 / 6.12.118 on 2026-11-17
the bug sat in the kernel just under four years and was opened by the fix for CVE-2022-3344
Nov 18
Terra Security research published 2026-11-18: a KVM use-after-free in nested virtualization on AMD CPUs lets a guest VM reach host memory - demonstrated on a DigitalOcean droplet reading about 127 GB of host RAM, and arbitrary write shown on the researchers' own bare-metal AMD server (32 chosen bytes into a live host kernel page)
The angle
A KVM bug let one cloud VM read 127 GB of host memory - how it hid in the kernel for four yearsSuggested format: Short video · for Developers, cloud/infra engineers, security watchers