UEFI bootkit bypasses Secure Boot on fully patched Windows machines
BlackX infections exploit Microsoft's mitigation gaps in Secure Boot protections, despite prior patches for CVE-2022-21894.
1 source · cross-referenced
- A new UEFI bootkit named BlackX has infected fully patched Windows machines by exploiting Microsoft's mitigation gaps in Secure Boot protections.
- The bootkit leverages the 'Baton Drop' logic flaw (CVE-2022-21894) in the Windows boot manager to bypass Secure Boot.
- Microsoft patched the underlying vulnerability in 2022 but did not fully revoke trust in older vulnerable boot managers until 2024, leaving a window for exploitation.
- Kaspersky researchers report that organizations failed to manually activate the mitigation, enabling the bootkit to achieve persistence and stealth.
- Microsoft has since directed customers to a Knowledge Base post, but it does not explicitly warn about the residual risk from the unrevoked certificate.
A newly documented UEFI bootkit named BlackX has infected fully patched Windows machines by exploiting gaps in Microsoft’s Secure Boot mitigations, according to research from Kaspersky. The bootkit leverages the 'Baton Drop' logic flaw in the Windows boot manager, tracked as CVE-2022-21894, which allows attackers to bypass Secure Boot and, in some conditions, extract BitLocker encryption keys.
Microsoft patched the underlying vulnerability in 2022, but the company did not immediately revoke trust in the digital certificate used to sign older vulnerable boot managers. In May 2023, Microsoft introduced a new signing certificate, Windows UEFI CA 2023, to Secure Boot’s trusted database, and in 2024 added a mitigation to block the older Windows Production PCA 2011 certificate via Secure Boot’s forbidden-signatures database. However, the 2024 mitigation did not fully revoke trust in the older certificate by default, leaving a window for exploitation.
Kaspersky researchers noted that most organizations did not take the additional manual step required to activate the mitigation after installing the patches. The researchers assessed that the instructions for enabling the mitigation were buried in a Microsoft Knowledge Base article and were difficult for average IT administrators to notice. The BlackX campaign likely succeeded because threat actors anticipated that organizations would overlook the need for manual activation.
Microsoft has since directed customers to a Knowledge Base post published two weeks prior to the report, but the guidance does not explicitly warn that the patches alone do not protect against Baton Drop attacks. The company’s response underscores the operational tension between revoking widely used certificates to close security gaps and the risk of rendering systems unbootable if the revocation occurs before the new certificate is widely deployed.
UEFI bootkits like BlackX and its predecessor BlackLotus are particularly dangerous because they execute early in the boot process, allowing attackers to load malicious drivers into the Windows kernel before many operating system and security defenses are operational. These bootkits can be difficult to detect without specialized tools and may persist even after an OS reinstallation if the infected boot partition remains intact.
- Nov 11, 2026 · Schneier on Security
Three arrested in multi-country scheme using AI to impersonate executives and lawyers in $129M fraud
Trust79 - Nov 10, 2026 · Ars Technica — Technology Lab
Grok Build link-sharing design exposes 35,000 apps and sensitive user data
Trust79 - Nov 10, 2026 · Schneier on Security
OpenSSH vulnerability allows login to password-disabled Alpine Linux accounts via oversized password
Trust79