[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpPVd_Sy5hSLkdWzotX198yg5RkweKYiMsaSQg6EJ0x8":3},{"article":4,"iocs":46,"watch_terms":54,"solutions":55,"lesson":119},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":28,"category":29,"article_tags":33},"334c597f-9faf-4e15-9f39-eba0c29b4684","Veeam warns of Software Appliance boot failures on AMD EPYC hosts","veeam-warns-of-software-appliance-boot-failures-on-amd-epyc-hosts-ea5950","​Veeam warned customers about boot failures affecting Software Appliance virtual machines (VMs) on hosts with AMD EPYC processors. [...]","Veeam has alerted customers to boot failures affecting its Software Appliance virtual machines when running on hosts with AMD EPYC processors. The issue stems from FIPS-mode jitterentropy health checks within the Linux kernel, which intermittently fail on certain EPYC CPUs, causing a kernel panic during early boot. Veeam advises redeploying the appliance to a different host or disabling automatic updates as a mitigation.","Veeam warns of boot failures for its Software Appliance VMs on AMD EPYC hosts due to FIPS kernel checks.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fveeam-software-appliance-vms-fail-to-boot-on-amd-epyc-hosts\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2026\u002F11\u002F06\u002FVeeam.jpg","2026-11-06T15:25:31+00:00","2026-11-06T16:00:18.702704+00:00",7,[17,20,23,26],{"name":18,"type":19},"Software Appliance","product",{"name":21,"type":22},"Veeam","vendor",{"name":24,"type":25},"AMD EPYC","technology",{"name":27,"type":25},"Linux kernel","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":28,"icon":30,"name":31,"slug":32},null,"Vulnerabilities","vulnerabilities",[34,39,41],{"category":35},{"id":36,"icon":30,"name":37,"slug":38},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":40},{"id":28,"icon":30,"name":31,"slug":32},{"category":42},{"id":43,"icon":30,"name":44,"slug":45},"89f78b1c-3503-45a1-9fc7-e23d2ce1c6d5","Malware","malware",[47,50],{"type":45,"value":48,"context":49},"jitterentropy","FIPS health check that fails on certain AMD EPYC processors, causing kernel panics.",{"type":51,"value":52,"context":53},"cve","CVE-2026-98432","Critical Linux kernel vulnerability in IPv4 TCP networking code affecting some Veeam products.",[21,18],{"controls":56,"vendors":113},[57,85],{"slug":58,"name":59,"problem":60,"products":61},"patch-management","Automated patch management","Known holes get closed in days, not months.",[62,69,77],{"vendor_slug":63,"vendor_name":64,"vendor_logo":65,"product_slug":58,"product_name":66,"url":67,"description":68},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":70,"vendor_name":71,"vendor_logo":72,"product_slug":73,"product_name":74,"url":75,"description":76},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":78,"vendor_name":79,"vendor_logo":80,"product_slug":81,"product_name":82,"url":83,"description":84},"ivanti","Ivanti","\u002Fvendor-logos\u002Fivanti.png","neurons-patch-management","Ivanti Neurons for Patch Management","https:\u002F\u002Fwww.ivanti.com\u002Fproducts\u002Fivanti-neurons-for-patch-management","Risk-based patch management for operating systems and third-party applications.",{"slug":86,"name":87,"problem":88,"products":89},"asset-inventory","Cyber asset inventory","You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.",[90,98,106],{"vendor_slug":91,"vendor_name":92,"vendor_logo":93,"product_slug":94,"product_name":95,"url":96,"description":97},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-cyber-assets","Axonius Cyber Assets","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fcyber-assets","A continuously reconciled view of every asset, who owns it, which security controls cover it and where it drifts from policy.",{"vendor_slug":99,"vendor_name":100,"vendor_logo":101,"product_slug":102,"product_name":103,"url":104,"description":105},"runzero","runZero","\u002Fvendor-logos\u002Frunzero.png","runzero-platform","runZero Platform","https:\u002F\u002Fwww.runzero.com\u002Fplatform\u002F","Finds and fingerprints everything on the network and in the cloud, including IoT and OT devices, without agents or credentials, and flags exposures.",{"vendor_slug":107,"vendor_name":108,"vendor_logo":109,"product_slug":110,"product_name":108,"url":111,"description":112},"lansweeper","Lansweeper","\u002Fvendor-logos\u002Flansweeper.png","lansweeper-asset-inventory","https:\u002F\u002Fwww.lansweeper.com\u002Fproduct\u002Fasset-inventory\u002F","Discovery with and without agents that keeps one central, always-updated inventory of devices, software and their details.",[114],{"slug":115,"name":21,"logo_path":116,"roles":117},"veeam","\u002Fvendor-logos\u002Fveeam.png",[118],"affected",{"slug":120,"title":121,"body":122,"framework_refs":123,"framework_notes":131},"veeam-appliance-boot-failures-on-amd-epyc-hosts-highlight-update-and-config-risks","Veeam Appliance Boot Failures on AMD EPYC Hosts Highlight Update and Config Risks","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.",[124,125,126,127,128,129,130],"CIS Control 7: Continuous Vulnerability Management","NIST SP 800-53 SI-2: Flaw Remediation","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","CIS Control 17: Incident Response Management","OWASP A06:2021 Vulnerable and Outdated Components","DORA Article 9",{"DORA Article 9":132,"NIST SP 800-53 SI-2: Flaw Remediation":133,"CIS Control 17: Incident Response Management":134,"OWASP A06:2021 Vulnerable and Outdated Components":135,"CIS Control 7: Continuous Vulnerability Management":136,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":137,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":138},"DORA requires financial entities to ensure ICT resilience including continuity of backup systems; a boot-failing backup appliance directly threatens the operational resilience mandated by this regulation.","SI-2 requires organizations to test software updates before installation; had Veeam updates been tested against AMD EPYC hosts in a controlled manner, the kernel panic would have been caught before impacting production.","Veeam's mitigation guidance — redeploying or disabling updates — constitutes an incident response action; organizations should have pre-defined runbooks for backup appliance failures to execute these steps rapidly without data protection gaps.","This category covers risks from software components behaving unexpectedly; the Linux kernel's jitterentropy implementation interacting poorly with specific CPUs is a component-level compatibility failure with direct availability consequences.","While this issue stems from a compatibility bug rather than a CVE, the guidance to test and stage updates before production deployment directly applies — unvalidated automatic updates introduced the boot failure.","This control requires organizations to manage technical vulnerabilities in a timely and consistent manner, including evaluating the risk of applying — or temporarily withholding — patches when compatibility issues arise.","FIPS mode is a security-hardening requirement often tied to compliance mandates; its failure here shows that enabling cryptographic compliance controls must be validated against the full hardware stack to avoid availability impacts."]