Emergency security mitigation on 7 Jul 2026 05:21:46 (UTC+00:00)
Update on 7 Jul 2026 05:22:17 (UTC+00:00)
The emergency maintenance across our KVM infrastructure has now been completed.
This maintenance was required because of a critical Linux KVM hypervisor vulnerability that was publicly disclosed. The issue could allow a guest virtual machine to crash the host system or, in more severe cases, escape from the guest environment to the host. You can read the technical disclosure here: https://thehackernews.com/2026/07/16-year-old-linux-kvm-flaw-lets-guest.html
Due to the severity of this vulnerability, we had to act quickly to protect customer data and the stability of our infrastructure. The work was carried out during the night to keep the impact on active services as low as possible. During the rollout, virtual machines were shut down gracefully where possible so operating systems could stop cleanly.
As part of the mitigation, the CPU type for affected virtual machines has been changed from "Host" to a standard compatible CPU profile. Nested Virtualization is currently disabled as a precaution. We are monitoring upstream kernel patches closely, and once a reliable patch is available and tested, we aim to make Nested Virtualization available again upon request.
We apologize for the short notice and for any disruption this emergency maintenance may have caused. If your server has not recovered as expected, or if you are experiencing any related issues, please open a support ticket and we will assist you as soon as possible.
The emergency maintenance across our KVM infrastructure has now been completed.
This maintenance was required because of a critical Linux KVM hypervisor vulnerability that was publicly disclosed. The issue could allow a guest virtual machine to crash the host system or, in more severe cases, escape from the guest environment to the host. You can read the technical disclosure here: https://thehackernews.com/2026/07/16-year-old-linux-kvm-flaw-lets-guest.html
Due to the severity of this vulnerability, we had to act quickly to protect customer data and the stability of our infrastructure. The work was carried out during the night to keep the impact on active services as low as possible. During the rollout, virtual machines were shut down gracefully where possible so operating systems could stop cleanly.
As part of the mitigation, the CPU type for affected virtual machines has been changed from "Host" to a standard compatible CPU profile. Nested Virtualization is currently disabled as a precaution. We are monitoring upstream kernel patches closely, and once a reliable patch is available and tested, we aim to make Nested Virtualization available again upon request.
We apologize for the short notice and for any disruption this emergency maintenance may have caused. If your server has not recovered as expected, or if you are experiencing any related issues, please open a support ticket and we will assist you as soon as possible.
Resolved on 7 Jul 2026 05:21:46 (UTC+00:00)
We performed a short reboot of the KVM servers during the night due to a required security mitigation on the hypervisor level.
The downtime was only around 30 seconds to 1 minute. This should be a single short interruption, and we do not expect any further downtime.
As part of the mitigation, we also need to change the CPU type of the virtual machines from "Host" to a standard compatible CPU profile. Nested Virtualization, running a VM inside a VM, will be disabled for now as a precaution.
If an official kernel patch becomes available later, we will apply it and can re-enable Nested Virtualization for your server on request.
We apologize for the short interruption and thank you for your understanding.
We performed a short reboot of the KVM servers during the night due to a required security mitigation on the hypervisor level.
The downtime was only around 30 seconds to 1 minute. This should be a single short interruption, and we do not expect any further downtime.
As part of the mitigation, we also need to change the CPU type of the virtual machines from "Host" to a standard compatible CPU profile. Nested Virtualization, running a VM inside a VM, will be disabled for now as a precaution.
If an official kernel patch becomes available later, we will apply it and can re-enable Nested Virtualization for your server on request.
We apologize for the short interruption and thank you for your understanding.