KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312) (cve.org)
fwsgonzo 2 hours ago
rootnod3 2 hours ago
That does not seem to be what HN has been thinking for months.
xmodem 2 hours ago
Agree that the article is downright painful to read though.
JoshTriplett 2 hours ago
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 2 hours ago
If you're running multitenant for mutually-untrusting customers, that excuse goes out the window.
JoshTriplett 2 hours ago
tptacek 2 hours ago
JoshTriplett an hour ago
(Aside: my current guess at the appropriate security posture towards Nitro Sandboxes, in the current era of vulnerabilities, is "decent, but probably has security holes too, and is less widely scrutinized, don't count on it either". Thoughts?)
Any recommendations for good guides on that, besides "design very careful IAM policies and security groups, harden any common services they have access to, and ideally run them under separate AWS accounts"?
necovek an hour ago
Do your lambda functions always get a per-customer dedicated instance or is firecracker distributing them so that multiple customers can have VMs on the same actual box?
Sounds like it would be pretty expensive for Amazon to dedicate an instance to every customer, especially for those with small workloads.
If that's the case, why would it not hold for Amazon but would hold for everyone else?
swiftcoder 42 minutes ago
At some point in the past they did, for pretty much exactly this reason. I'd assume they don't anymore (I last worked there a decade ago).
TZubiri an hour ago
gerdesj an hour ago
veverkap an hour ago
adverbly an hour ago
CVE still listed...
praseodym 2 hours ago
Betelbuddy 2 hours ago
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 2 hours ago
catlifeonmars an hour ago
cduzz 20 minutes ago
At first, there were just big logic blocks and storage that did as they were told.
Later, in hardware, there were all sorts of optimizations built in where the logic would do its own thing -- so you'd get caches and speculative execution and even on-the-fly conversion from one instruction set to another.
This abstraction was also piled onto the runtime -- you'd write machine code, then assembly, then higher level languages; eventually you'd run in interpreted or just-in-time generated bytecode (hello to Java from UCSD p-System from the 70s and Burroughs machines in the 60s). And of course... operating systems...
Now, we've got machines reading source code (and machine code, and everything in between) and they've got some ability to thing the thing to make it thing. Sometimes correctly (enough to pass existing tests) and sometimes without the ability to express to the human what the thing they thinged was.
But, we're all living in the land of mel and for some it's always been better to go fishing than to pretend to participate.
xlayn an hour ago
drum55 an hour ago
cluckindan an hour ago
bigfishrunning an hour ago
Ylpertnodi 44 minutes ago
sylos an hour ago
tptacek an hour ago
tsunagatta 31 minutes ago
mahogany 8 minutes ago
catlifeonmars an hour ago
manbash an hour ago
Also in this case, a "missed potential" if it eventually fails to reach anyone.
InsidiousWombat 41 minutes ago
biotechbio an hour ago
JeremyNT 23 minutes ago
Perhaps they are rewriting it with less slop?
The CVE itself: https://www.cve.org/CVERecord?id=CVE-2026-99312
arde an hour ago
jacobgold 2 hours ago
dvh 2 hours ago
SOLAR_FIELDS 2 hours ago
dvh 2 hours ago
voakbasda an hour ago
hparadiz an hour ago
punchmesan an hour ago
Sure, some projects are trying to be responsible or are trying to keep waves of slop PR's from drowning them, but that is by no means an indication of a general distaste for AI code. It's been largely embraced.
the8472 2 hours ago
j45 2 hours ago
tptacek 2 hours ago
tyingq 2 hours ago
MajesticHobo2 an hour ago
hparadiz an hour ago
catlifeonmars an hour ago
vbezhenar 32 minutes ago
hparadiz 28 minutes ago
TZubiri an hour ago
InsidiousWombat 39 minutes ago
sadkgasjdfgk 10 minutes ago
gbrindisi 2 hours ago
wmf an hour ago
rvz 29 minutes ago
eyberg 3 minutes ago
cloudie78 30 minutes ago
Just don’t.
adverbly an hour ago
Honestly, this gives me pause on the whole "VM is sufficient for any agentic sandbox environment" theory.
Ungh an hour ago
kristjank an hour ago
tptacek 44 minutes ago
Ungh 32 minutes ago
bigbuppo an hour ago
LelouBil 26 minutes ago
ArcHound 2 hours ago
In the meantime the patching will continue until security improves!
j45 2 hours ago
nubinetwork 2 hours ago
calvinmorrison 2 hours ago
j45 2 hours ago
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.
stilldavid 2 hours ago
pixl97 an hour ago
tptacek 2 hours ago
Don't allow nested KVM.
rwmj 2 hours ago
tptacek 2 hours ago
k0morebi an hour ago
pixl97 an hour ago
FLeXMurphy an hour ago