Microsoft's Secure Boot, an industry-standard security measure, has been compromised for over a decade, and the tech giant only recently acknowledged the issue. This oversight has significant implications for both Windows and Linux users, as it exposes a critical vulnerability in the system's core security mechanism. The problem lies in the use of 'shims' - secondary trust anchors signed by Microsoft that authorize subsequent software loading during the boot process. These shims, designed to extend Secure Boot to Linux devices, have been left unsigned and unrevoked, allowing attackers to bypass the protection with relative ease. The discovery by ESET researchers highlights a critical flaw in Microsoft's oversight, as the company failed to revoke 11 defective firmware images, some dating back to 2013. This lapse has enabled attackers to install malicious firmware, subvert the mandated chain of digitally signed firmware, and persist after OS reinstallation or hard drive replacement. The complexity of Secure Boot's revocation process, which relies on databases and version-based mechanisms, has contributed to this issue. The threat extends to both Windows and Linux users, as the shim can be installed on devices running either operating system. The implications are particularly concerning given the history of bootkits, such as LoJax, MosaicRegressor, CosmicStrand, and BlackLotus, which have exploited similar vulnerabilities. The fact that these vulnerable shims have been left unsigned for over a decade raises serious questions about the effectiveness of Secure Boot as a security measure. It also underscores the need for a more robust and transparent revocation process, as well as a reevaluation of the entire secure boot model. The complexity of the system, combined with Microsoft's role as the de facto root of trust, has created a situation where the protection is not as secure as it should be. This debacle serves as a stark reminder of the importance of vigilance and proactive security measures in the face of evolving threats. In my opinion, this incident highlights the need for a more comprehensive and transparent approach to security, one that involves regular audits and updates to ensure the system's integrity. It also underscores the importance of collaboration between hardware makers and software companies to address security vulnerabilities in a timely and effective manner.