Veeam has notified its customer base of a critical boot issue impacting Software Appliance virtual machines running on hosts powered by AMD EPYC processors. The Software Appliance represents a pre-built, Linux-based VM deployment that enables administrators to run Veeam Backup & Replication without the overhead of manual dependency installation or software configuration.
To meet compliance requirements imposed by corporate and government security standards, the underlying Linux kernel executes integrated cryptographic and health verification routines (including jitterentropy health tests) in FIPS mode during the initial boot sequence. On certain AMD EPYC processor variants, however, these VMs fail to complete the boot process and trigger a kernel panic after the early-boot FIPS-mode jitterentropy check fails.

A Veeam Software Appliance (Linux-based Veeam Backup & Replication) virtual machine running on a host with an AMD EPYC processor intermittently fails to boot after a reboot, including a reboot that follows an update that installs a new kernel
Veeam advisory
Veeam elaborated that the jitterentropy health test running in FIPS mode during early boot intermittently fails on specific AMD EPYC processor models, namely the 7262, 7302, and 7F72. When this test fails, the kernel halts the boot sequence and generates a kernel panic.
The root cause traces back to the Linux kernel version bundled with the Veeam Software Appliance. The issue affects Veeam Software Appliance version 13.1 and all subsequent releases. Administrators encountering this problem observe the error message "Kernel panic - not syncing: jitterentropy: Initialization failed with host not compliant with requirements: 9" on affected systems.
Mitigation options
Veeam recommends redeploying the appliance onto a Linux host equipped with a different processor as the primary mitigation strategy. For environments where such redeployment is not feasible, IT administrators should disable automatic updates on the appliance and apply updates manually while closely monitoring the VM during reboots.
If the kernel panic occurs, power off the virtual machine and power it on again. A restart of the guest operating system does not recover the virtual machine. After the appliance has booted successfully, no further errors are expected, and the operation of Veeam Backup & Replication is not affected.
Veeam
Additional vulnerability disclosure
In a separate announcement released the same day, Veeam disclosed that multiple products are vulnerable to a critical Linux kernel flaw designated CVE-2026-98432. This vulnerability resides in the IPv4 TCP networking subsystem and permits unauthenticated remote attackers to achieve root-level code execution on servers that have Multipath TCP (MPTCP) listeners enabled.
Veeam has already remediated the CVE-2026-98432 vulnerability in certain affected components and is distributing the patched kernel to impacted systems through either private fixes or the Veeam Updater mechanism.
Veeam maintains a customer base exceeding 550,000 organizations worldwide, encompassing 74% of Global 2,000 companies and 82% of Fortune 500 enterprises.