Veeam warns of Software Appliance boot failures on AMD EPYC hosts

Veeam alerted clients about boot failures impacting Software Appliance virtual makers(VMs)on hosts with AMD EPYC processors.

The business’s Software Appliance VMs are pre-configured, Linux-based virtual makers that let admins run the Veeam Backup & & Replication backup software application suite on Linux gadgets without by hand setting up reliances or setting up the software application.

To adhere to business and federal government security structures, the underlying Linux kernel runs incorporated health and cryptographic checks (such as jitterentropy health tests) in FIPS mode throughout early boot.

As the business discussed in a Wednesday advisory, these VMs will stop working to boot and will crash with a kernel panic after stopping working an early-boot FIPS-mode jitterentropy check on some AMD EPYC processors.

“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,” it stated

“This issue occurs because the Linux kernel used by the Veeam Software Appliance runs a jitterentropy health test in FIPS mode during early boot, and the test intermittently fails on certain AMD EPYC processors, including AMD EPYC 7262, 7302, and 7F72. When the test fails, the kernel stops the boot process with a kernel panic.”

This recognized concern comes from the Linux kernel variation utilized by the Veeam Software Appliance and impacts Veeam Software Appliance variation 13.1 and later on.

According to Veeam, users are seeing “Kernel panic – not syncing: jitterentropy: Initialization failed with host not compliant with requirements: 9” kernel panic mistakes on affected systems.

news Mitigation offered

To reduce this problem, Veeam informed IT administrators to redeploy the home appliance to a Linux host with a various processor.

If the home appliance can not be redeployed on a system with an untouched processor, IT admins are recommended to disable automated updates for the device and set up updates by hand (while keeping track of the VM as it restarts).

“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,” Veeam included. “After the appliance has booted successfully, no further errors are expected, and the operation of Veeam Backup & Replication is not affected.”

Earlier today, Veeam likewise stated that a few of its items are impacted by a vital Linux kernel vulnerability (CVE-2026-98432) in the IPv4 TCP networking code that permits remote unauthenticated assailants to carry out commands as root on servers running Multipath TCP (MPTCP) listeners.

The business has actually repaired the CVE-2026-98432 defect for some affected Veeam elements and is now pressing the covered kernel to impacted systems either as a personal repair or through the Veeam Updater.

Veeam’s items are utilized by more than 550,000 clients, consisting of 74% of Global 2,000 companies and 82% of Fortune 500 business.

news

Discover e-mail hazards your existing defenses might miss out on.

Adaptive Security’s AI representatives examine e-mail intent, context, and habits to reveal phishing, company e-mail compromise, and billing scams.

See what’s surviving with a 14-day read-only scan of Microsoft 365 or Google Workspace, without any MX modifications.

Start your complimentary e-mail security scan.