CVE-2026-99312: KVM Guest-to-Host Escape (terra.security)

119 points by Kozmik1 2 hours ago

praseodym an hour ago

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

xlayn an hour ago

doesn't change the value of what's writen, if true and actionable that's all that should be needed

manbash 16 minutes ago

It has "potential", not "value".

Also in this case, a "missed potential" if it eventually fails to reach anyone.

sylos 28 minutes ago

Value is more than just iron something is made from. How it's shaped and presented is just as important

tptacek 12 minutes ago

drum55 an hour ago

If it was valuable a human would have been able to communicate it in a few lines of text. Using a LLM to blast slop devalues everything and communicates little. A drunken twitter rant has more ability to convey information than sloppy blog posts with 3 pieces of information per sentence and a load bearing attitude.

Ylpertnodi 10 minutes ago

cluckindan 39 minutes ago

catlifeonmars 19 minutes ago

It kind of does, the OP could have just saved themselves the tokens and posted a 130 word summary on x/twitter that would have been just as useful.

InsidiousWombat 7 minutes ago

well it's 404 now

Betelbuddy an hour ago

The LLMs find the security issues, the LLMs will write the reports and the LLMs will fix and patch them.

I guess its time for all of us to step aside, leave space for somebody who knowns what they are doing, and go fishing...

praseodym an hour ago

And this way only LLMs can learn from these vulnerabilities, making it even more likely that the next one will be found by an LLM.

catlifeonmars 17 minutes ago

biotechbio an hour ago

Glad to see this is the top comment. This is written by Claude, I know because I talk to Claude for 8+ hours a day, and it says stuff like this. I stopped reading the article because of it.

jacobgold 2 hours ago

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

dvh 2 hours ago

Not necessarily. Only if you assume that no new insecure code is added. If ai found 1 security bugs in old code but ease of code generation with ai adds 2 new security issues (in unrelated code), then we are getting less secure.

tyingq an hour ago

Is it a given that it's as good at outputting secure code as it finding insecure code? That leaves a fair amount of room for people not baking in deep review steps. Also mentioned elsewhere, but if velocity is way up...that ramps up bugs anyway.

MajesticHobo2 an hour ago

SOLAR_FIELDS 2 hours ago

Do we have any evidence around the rate that AI emits security bugs vs humans previously? You would think that perhaps AI would be better about this, but perhaps not.

dvh an hour ago

the8472 an hour ago

tptacek an hour ago

I hate these meta conversations on crunchy technical topics and feel like we should be digging into the KVM security model more than this general security prognostication stuff. Having said that, I will hypocritically further this debate by pointing out that the determinant of software security moving forward is not so whether AI is drastically better than humans at avoiding common vulnerability patterns, (or instead just a little better). Rather, it's that AI will make it much easier to move subsystems or whole projects to memory-safe programming languages and towards formal verification.

j45 an hour ago

Existing code will have security holes that haven't been found yet.

InsidiousWombat 6 minutes ago

...if the pace of both fixing and finding bugs got accelerated, all we're in for is machines being on average more vulnerable (because patching takes time and effort and more bugs increases that)

TZubiri 13 minutes ago

Have you ever been told that you are problematically optimistic?

gerdesj an hour ago

404

veverkap 43 minutes ago

Same for me - did they remove it?

adverbly 38 minutes ago

fwsgonzo 2 hours ago

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.

xmodem an hour ago

Outside of development and CI, I have yet to hear a compelling use case for nested virtualization.

Agree that the article is downright painful to read though.

JoshTriplett an hour ago

> I have yet to hear a compelling use case for nested virtualization.

AWS instances are slow to launch; they take whole seconds. Nested virtualization allows running something like firecracker/crosvm/rust-vmm atop a normal AWS instance, without needing a bare-metal one.

tptacek an hour ago

TZubiri 12 minutes ago

? If you don't use it, disable it. Simple as that

rootnod3 an hour ago

> It really should be rewritten by a human.

That does not seem to be what HN has been thinking for months.

arde 42 minutes ago

That's a 404 now.

gbrindisi 2 hours ago

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

wmf 20 minutes ago

Unikernels that run on KVM aren't going to protect against KVM escapes.

adverbly an hour ago

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.

tptacek 2 hours ago

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.

rwmj an hour ago

Certain Windows features need it unfortunately. Virtualization-Based Security (VBS), Credential Guard, Hyper-V (obviously), and I'm going to say WSL2(?)

tptacek an hour ago

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.

Ungh 41 minutes ago

tptacek 11 minutes ago

Theo was wildly wrong about this, but he wrote it pithily so it's never going to die.

https://news.ycombinator.com/item?id=48883089

kristjank 15 minutes ago

There is a Theo quote for everything, isn't there...

ArcHound 2 hours ago

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!

j45 an hour ago

Doubt it, but there will be a big spike for a while and then slow down.

bigbuppo 21 minutes ago

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

nubinetwork 2 hours ago

I guess its time to shut off the internet.

calvinmorrison 2 hours ago

what is the mitigation.

stilldavid an hour ago

Look in the article under the headline "Mitigation".

pixl97 38 minutes ago

Page has gone 404.

j45 an hour ago

The cloud is somebody else's computer.

Mitigations are layered, first not using a shared VPS, and instead running your own bare metal server with something like proxmox to run the containerization.

Those containers could be susceptible to issues between them too, but you at least control the environment and can put more checks and balances in place.

Shared cloud and vps is going to become bumpy and more insecure the next little while. There's no way around it.

FLeXMurphy 16 minutes ago

Page is now 404'd.

k0morebi an hour ago

404 now

pixl97 38 minutes ago

Confirmed, wonder what happened here.