Back to all lessons
Awareness Lessons
last week

Veeam Appliance Boot Failures on AMD EPYC Hosts Highlight Update and Config Risks

Written by AI from the linked story. Not reviewed by an editor. How this works

A compatibility issue between Veeam's Software Appliance and AMD EPYC processors causes kernel panics during boot due to failing FIPS-mode jitterentropy health checks in the Linux kernel — a problem introduced or exposed through automatic updates. This matters because backup and recovery appliances are critical infrastructure; unexpected boot failures can render an organization's entire backup capability unavailable precisely when it's needed most. The incident illustrates the danger of applying automatic updates without validating compatibility across all hardware configurations in the environment. It also highlights that security-hardening features like FIPS mode can introduce unexpected instability if not rigorously tested against diverse hardware. Veeam's recommended workaround — disabling automatic updates — itself introduces a secondary risk of unpatched vulnerabilities remaining in production.

Tactical Insight

Immediate actions

  • Redeploy affected Veeam Software Appliances to non-AMD EPYC hosts as a temporary measure until a patched version is available.
  • Disable automatic updates on the appliance only as a short-term workaround, while establishing a manual patching schedule to avoid falling behind on security fixes.

Configuration & Compatibility Controls

  • Maintain a detailed hardware inventory mapping all virtual appliances to their underlying host processor architectures to quickly identify blast radius during hardware-specific issues.
  • Test updates in a staging environment that mirrors production hardware diversity — including AMD EPYC, Intel, and ARM variants — before allowing automatic rollout to production.
  • Document and track all FIPS-mode or security-hardening configurations separately, so their interaction with kernel and hardware updates can be validated before deployment.

Long-term improvements

  • Implement a change management process that requires vendor-confirmed hardware compatibility matrices before automatic updates are enabled on critical appliances.
  • Establish health-check monitoring on backup appliances to alert on boot failures or unexpected downtime, ensuring rapid detection of issues introduced by updates.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.