> but for unclear reasons, Microsoft patched it only last Tuesday I think it's obvious why Microsoft has only recent patched the issue: because Linux distros r

> but for unclear reasons, Microsoft patched it only last Tuesday I think it's obvious why Microsoft has only recent patched the issue: because Linux distros really lag behind on se curie issues like these. Hence the warning some people receive: they're still using a vulnerable boot configuration that was fixed two years ago. In a similar vein, Microsoft waited a year before automatically releasing a secure boot related patch that affected Windows, so system administrators wouldn't be blindsided: https://msrc.microsoft.com/blog/2023/05/guidance-related-to-secure-boot-manager-changes-associated-with-cve-2023-24932/ https://msrc.microsoft.com/blog/2023/05/guidance-related-to-... The impact of these patches is minor for most consumer devices, but for corporate environments where IT may need to go around entering Bitlocker recovery keys in some edge cases (and where recovery media needs to be made using a recent ISO or it won't work), people need a reasonable time to prepare.