News for hackers. Stuff that matters.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tptacek on Wednesday November 18, 2026 @11:57AM (#50548713)
Another nested KVM bug. We debated enabling nested KVM for many years, and held the line every time, because the only post-2020 KVM vulnerability we knew of required nested VMs. That decision aged well: we've gotten at least 2 more nested KVM escapes in the last year.

Don't allow nested KVM.

Re:CVE-2026-99312: KVM Guest-to-Host Escape by rwmj on Wednesday November 18, 2026 @12:21PM (#50549121)
Certain Windows features need it unfortunately.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tptacek on Wednesday November 18, 2026 @12:23PM (#50549150)
Right, sorry, that's a fair point (and Josh Triplett made another fair point earlier). I'm sort of implicitly locked in to the "hosting company" use case here: services running mutually-untrusting isolated workloads for customers.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by bonzini on Wednesday November 18, 2026 @03:38PM (#50551819)
KVM maintainer here. On one hand it's true that nested is the single biggest attack surface in the hypervisor, on the other hand it will be over relatively soon. Considering the LLMs have ~15 years of nested virtualization to catch up with, it's not in an awful state. These bugs are extremely complicated to exploit, which means that the past ten years of fuzzing with syzkaller have already found the low hanging fruit.