Security Updates and Reboots for KVM Host Nodes 15hr 32min ago
Resolved
We applied security updates to affected KVM host nodes in response to CVE-2026-99999, a critical Linux kernel vulnerability that may allow a malicious virtual machine to affect its host.
We initially waited for a KernelCare live patch to avoid interrupting customer virtual machines. As a suitable patch did not become available within an acceptable timeframe, we proceeded with kernel updates and reboots. Host nodes were patched and rebooted sequentially to limit the impact.
Customers may have experienced a service interruption of up to approximately 30 minutes while the node hosting their server was updated and restarted.
Customers running their own virtualization stack on dedicated servers, including KVM/QEMU, should assess whether their systems are affected and apply any required updates and reboots themselves. Dedicated servers were not part of this maintenance unless they were operated as part of our managed virtualization infrastructure.
We apologize for the short notice and any inconvenience. Given the potential guest-to-host impact, we could not delay patching further.
We applied security updates to affected KVM host nodes in response to CVE-2026-99999, a critical Linux kernel vulnerability that may allow a malicious virtual machine to affect its host.
We initially waited for a KernelCare live patch to avoid interrupting customer virtual machines. As a suitable patch did not become available within an acceptable timeframe, we proceeded with kernel updates and reboots. Host nodes were patched and rebooted sequentially to limit the impact.
Customers may have experienced a service interruption of up to approximately 30 minutes while the node hosting their server was updated and restarted.
Customers running their own virtualization stack on dedicated servers, including KVM/QEMU, should assess whether their systems are affected and apply any required updates and reboots themselves. Dedicated servers were not part of this maintenance unless they were operated as part of our managed virtualization infrastructure.
We apologize for the short notice and any inconvenience. Given the potential guest-to-host impact, we could not delay patching further.