KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

Kozmik1 183 points 121 comments November 18, 2026
www.cve.org · View on Hacker News

Discussion Highlights (18 comments)

gbrindisi

Thinking about agents sandboxes... it truly seems like the time is ripe for unikernels

nubinetwork

I guess its time to shut off the internet.

jacobgold

Our infrastructure will become so much more secure but we're in for a bumpy ride through 2027.

ArcHound

Surely, we'll run out of critical CVEs in open-source someday. Seems it's not today. In the meantime the patching will continue until security improves!

tptacek

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.

fwsgonzo

Don't disable nested, it's still better security than everything else, and having it on means access to real hardware virtualization. Second, the article is AI-written. It really should be rewritten by a human.

calvinmorrison

what is the mitigation.

praseodym

The blog post is very difficult to read, I suspect that unfortunately it’s fully written by an LLM.

adverbly

Well this sucks. So this needs a kernel fix then? Looks like I can disable nested passthrough manually, but am I stuck waiting for downsteam fixes at this point then? Honestly, this gives me pause on the whole "VM is sufficient for any agentic sandbox environment" theory.

arde

That's a 404 now.

Ungh

Time to dig this one out again https://marc.info/?l=openbsd-misc&m=119318909016582

bigbuppo

Looking forward to Ubuntu finally rolling out an updated kernel for this in the year 2057.

FLeXMurphy

Page is now 404'd.

cloudie78

Nested virtualisation. Just don’t.

LelouBil

At this point, I'm just hoping the attackers get choice paralysis when thinking about which exploit to use.

sadkgasjdfgk

I wonder if AWS' Nitro Sandboxes would prevent this?

immibis2

Links to a CVE record. The kernel project marks everything that could conceivably be of any use to an attacker as a CVE. What are we actually looking at here? Sounds like a dangling-pointer type of bug?

snvzz

I don't get the insistence on using Linux as hypervisor knowing how bad it is, instead of the far more appropriate choice, seL4[0]. 0. https://sel4.systems/

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed