Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX news · Global

Veeam Warns of Boot Failures on AMD EPYC Hosts and Critical Kernel Vulnerability

Based on reporting from BleepingComputer

Published by the source: Fri, 06 Nov 2026 10:25:31 -0500

AEGLIX News

Veeam has warned that its Software Appliance version 13.1 and later can experience boot failures on certain AMD EPYC processors, including the 7262, 7302, and 7F72 models, due to an intermittent failure in the jitterentropy health test that triggers a kernel panic in the underlying Linux kernel.

The issue stems from the Linux kernel version used by the Veeam Software Appliance and affects deployments running on the identified AMD EPYC CPUs. Veeam products are widely deployed, with the company reporting more than 550,000 customers, including 74% of Global 2,000 firms and 82% of Fortune 500 companies, indicating a broad potential footprint for the boot failure.

The jitterentropy health test intermittently fails on the affected AMD EPYC processors, causing a kernel panic during the boot process. Veeam notes that after a successful boot, no further errors are expected and Veeam Backup & Replication operation is not affected. Separately, the company disclosed that some products are impacted by a critical Linux kernel vulnerability, CVE-2026-98432, in IPv4 TCP networking code that could allow remote unauthenticated attackers to execute commands as root on servers running MPTCP listeners.

Veeam recommends redeploying the appliance to a Linux host with a different processor as the primary mitigation. If redeployment is not possible, administrators should disable automatic updates and install updates manually while monitoring the virtual machine as it reboots. For the critical kernel vulnerability CVE-2026-98432, Veeam has fixed the issue for some impacted components and is pushing the patched kernel via private fix or through the Veeam Updater.

Report prepared 2026-11-06 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.

Sources

Read original source · BleepingComputer (opens in a new tab)

Privacy policy

Explore the story

Consult the cited publisher for the original reporting, updates and supporting evidence. Check the publication date and source before acting on a headline.

These are research tools; no CVE, indicator, or campaign relationship is inferred from this article.

More from BleepingComputer

← Back to security news