Hang on a second. Something smells funny.
Shirley this is a hole in SecureBoot, not in GRUB2?
Yes, GRUB2 has a bug that makes exploiting the hole somewhat easier ... But any bootloader can easily[0] open the same hole in SecureBoot, so blaming GRUB2 for this seems a trifle misguided.
Besides, if I have access to the hardware I own it anyway (as pointed out in the article).
I also note with interest that there isn't any mention of this at https://www.gnu.org/software/grub/ ... and the latest download release is dated July 5th of last year.
I'm probably missing something. Wouldn't be the first time. Anybody have any input? I'm buying.
Note: I don't have a dog in this race ... I don't use GRUB.
[0] "Easy" is subjective, and bootloaders aren't exactly rocket surgery. Bear with me.