
A continuous integration (CI) runner can report a freshly updated kernel while the physical server beneath it still needs a patch. CVE-2026-99312 affects Linux’s Kernel-based Virtual Machine (KVM) on AMD systems running nested virtual machines. If your runner boots VMs of its own, verify the fix on the physical server that hosts it. Linux kernel CVE record
Take a team that tests a Linux installer. A physical AMD server runs KVM (level 0, or L0). One of its VMs is the CI runner (L1). For each test, the runner boots the installer in a disposable VM (L2). Each guest has its own view of memory, and KVM tracks how to translate addresses for whichever guest is running. Linux guide to nested KVM
On an affected host, KVM can resume the runner after a virtual CPU initialization event (INIT) with the test VM’s memory-translation state still in use. The patch makes KVM reset its memory management unit (MMU) context every time it emulates that event. The maintainers narrowed the flaw to AMD’s nested Secure Virtual Machine (SVM) implementation. Intel’s VMX intercepts the event before it can reach this path. Upstream KVM fix
uname -r and read /sys/module/kvm_amd/parameters/nested. A value of 1 or Y means nesting is enabled. Check which runner VMs can use the virtualization extension. Pools that never run nested guests can keep nesting disabled. If a cloud provider operates the physical host, ask it to confirm the patch status for that pool. Linux nested KVM configuration7.3.5-1 as fixed in unstable and tracks its other releases separately. Upstream version record · Debian package statusA guest can reach the affected KVM code even when SSH to the host is locked down. The kernel update corrects the memory handling. Adaptive lets the virtualization team decide who can inspect those hosts, change their configuration, and install the patch.

