Video games news, releases, esports and culture — all the biggest gaming stories in one place.
Turns out Microsoft’s Secure Boot was little better than a busted lock for about a decade
Microsoft has revoked trust for 11 vulnerable UEFI shim bootloaders after researchers found they could be used to bypass Secure Boot, a protection designed to stop unauthorised code running during start-up. The flaw could allow malicious firmware to persist even after a hard drive replacement or operating-system reinstallation, affecting both Windows and Linux systems.
The shims, used to help Linux systems work with Secure Boot, were signed using Microsoft’s UEFI CA 2011 certificate and appeared in Linux distributions and PC diagnostic tools. ESET reported the 11 vulnerable shims in February, and Microsoft revoked them in its June monthly update; at least one reported weakness had reportedly been publicly documented for about a decade.
In short
- Microsoft revoked 11 bootloaders that could bypass Secure Boot.
- Malware could persist beyond drive changes or OS reinstalls.
- One vulnerability had reportedly been known for around a decade.
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
This represents a significant security failure that demands explanation. A cornerstone protection against unauthorised firmware execution remained fundamentally compromised for approximately a decade, with at least one vulnerability publicly documented throughout this period. The extended timeline from ESET's February report to Microsoft's June revocation, combined with prolonged public knowledge going unresolved, suggests insufficient vigilance in monitoring and maintaining the security of signed components critical to system integrity.
The case against
Firmware vulnerabilities in complex, distributed ecosystems are inherently difficult to identify and remediate comprehensively. These bootloaders were maintained by multiple third parties primarily for Linux compatibility with Secure Boot. The process from ESET's research through Microsoft's investigation and revocation reflects responsible security practices functioning appropriately: vulnerabilities are identified, thoroughly investigated, and protective measures implemented. That the system ultimately protected users by revoking trust in the compromised components demonstrates the security framework succeeding.
Explained simply
Secure Boot is a security feature that runs when you start your computer, checking that only trusted software loads before Windows or Linux begins. Its job is to stop malicious code taking control at this early stage, when ordinary security software cannot yet protect you.
Some compatibility tools, called shims, were created to help Linux systems work with Secure Boot on newer computers. Microsoft approved and signed these tools as trustworthy, but researchers found that certain versions contained flaws that could be exploited to bypass Secure Boot's protections.
If malware exploited these weaknesses, it could embed itself so deeply in your computer that it would survive replacing your hard drive or reinstalling the whole operating system. The problem reportedly existed for roughly ten years before being widely identified, leaving many systems potentially vulnerable during that extended period.