UEFI CA 2011 revocations to remain mandatory - #460
Open
jcoester wants to merge 1 commit into
Open
Conversation
UEFI CA 2011 revocations need to remain mandatory because systems with dedicated GPUs may depend on UEFI CA 2011. As Windows Update currently skips applying optional revocations after unrelated PCA 2011 is revoked, marking these UEFI CA 2011 revocations as “optional” leaves systems vulnerable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This has been discussed repeatedly and remains a security issue, still unresolved as of 29th August 2026:
Three Canonical images signed by Microsoft Corporation UEFI CA 2011 are marked as
isOptional, meaning Windows Update does not automatically apply these revocations on my latest 25H2 (Build 26200.9278), and I had to append them via firmware Secure Boot Key Management.While Microsoft Corporation UEFI CA 2011 is expired, it remains quasi-required for Windows systems with dedicated graphics cards for many years to come. The affected three Canonical images are associated with a wide range of known Secure Boot vulnerabilities: CVE-2020-10713, CVE-2020-14308, CVE-2020-14309, CVE-2020-14310, CVE-2020-14311, CVE-2020-15705, CVE-2020-15706, CVE-2020-15707.
Strongly suggest keeping these three UEFI CA 2011 revocations mandatory so the intended Secure Boot protection is automatically applied through Windows Update.
Maybe it can be clarified why the optional revocations are not rolled out on systems with the respective certs present; in which case they are not optional. As suggested before, future rollouts may use DB-aware DBX servicing to prevent major security gaps and optimize NVRAM storage (#447).