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.
show comments
gerdesj
404
show comments
sadkgasjdfgk
I wonder if AWS' Nitro Sandboxes would prevent this?
praseodym
The blog post is very difficult to read, I suspect that unfortunately it’s fully written by an LLM.
show comments
arde
That's a 404 now.
jacobgold
Our infrastructure will become so much more secure but we're in for a bumpy ride through 2027.
show comments
gbrindisi
Thinking about agents sandboxes... it truly seems like the time is ripe for unikernels
show comments
cloudie78
Nested virtualisation.
Just don’t.
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.
Looking forward to Ubuntu finally rolling out an updated kernel for this in the year 2057.
LelouBil
At this point, I'm just hoping the attackers get choice paralysis when thinking about which exploit to use.
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!
show comments
nubinetwork
I guess its time to shut off the internet.
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 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.
404
I wonder if AWS' Nitro Sandboxes would prevent this?
The blog post is very difficult to read, I suspect that unfortunately it’s fully written by an LLM.
That's a 404 now.
Our infrastructure will become so much more secure but we're in for a bumpy ride through 2027.
Thinking about agents sandboxes... it truly seems like the time is ripe for unikernels
Nested virtualisation.
Just don’t.
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.
Time to dig this one out again https://marc.info/?l=openbsd-misc&m=119318909016582
Looking forward to Ubuntu finally rolling out an updated kernel for this in the year 2057.
At this point, I'm just hoping the attackers get choice paralysis when thinking about which exploit to use.
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!
I guess its time to shut off the internet.
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.
what is the mitigation.
404 now
Page is now 404'd.