A flaw that could let code inside a virtual machine reach the server underneath it was published on 18 November as CVE-2026-99312, rated 8.8 out of 10 in its CVE record. Our AMD virtualization servers now run a kernel with the fix, and on a seedbox you have nothing to do.
What it was
First the origin; then the cure. The Linux kernel's CVE record describes a bug in nested virtualization on AMD processors, the feature that lets a virtual machine run virtual machines of its own. Intel processors are not affected. To use the flaw, an attacker needs access to the KVM device (/dev/kvm) inside a guest. Seedbox accounts have no root and cannot open that device on the servers we checked, so an attack would first have needed administrator access inside a guest.
What we did
I installed the fixed kernel on our AMD virtualization servers, rebooted each one, and turned nested virtualization off on them. Nothing in our seedbox software used it.
What you saw
Each of those servers was restarted between 19 November and the morning of 20 November (UTC). Per-server back-online emails covered most of these restarts. A few servers took longer to come back than I wanted, and I am sorry for that wait. If your seedbox restarted and you received no email, this is the notice. If anything on it still looks wrong, open a ticket.
What you need to do
On a seedbox: nothing. If you run your own KVM host, for example on a dedicated server, check it. On an AMD machine, cat /sys/module/kvm_amd/parameters/nested prints 1 or Y when nested virtualization is on. If it does, update the host kernel to a release that carries the fix (upstream stable 6.12.118, 6.18.64, 7.3.5 or newer; Proxmox kernel 7.0.14-30 or newer) and reboot, or set options kvm_amd nested=0 in /etc/modprobe.d/ and reboot.
Best Regards,
Väinämöinen
Pulsed Media Support
(Ilmarinen forged the Sampo; I patch the kernels)
Friday, November 20, 2026
