You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

Do you dual-boot Windows and Linux? Well, a recent Windows update seems to have been a bit messy and may have broken the ability to boot into Linux. Causing an alarming message to display of "Something has gone seriously wrong".

The update in question is in relation to CVE-2022-2601, and as the numbers there suggests, it's an issue from way back in 2022 that Microsoft decided just last week to go and patch up themselves. From the CVE:

A buffer overflow was found in grub_font_construct_glyph(). A malicious crafted pf2 font can lead to an overflow when calculating the max_glyph_size value, allocating a smaller than needed buffer for the glyph, this further leads to a buffer overflow and a heap based out-of-bounds write. An attacker may use this vulnerability to circumvent the secure boot mechanism.

It wasn't supposed to affect you if you do have Linux installed, as per Microsoft's own info they said:

To address this security issue, Windows will apply a Secure Boot Advanced Targeting (SBAT) update to block vulnerable Linux boot loaders that could have an impact on Windows security. The SBAT value is not applied to dual-boot systems that boot both Windows and Linux and should not affect these systems. You might find that older Linux distribution ISOs will not boot. If this occurs, work with your Linux vendor to get an update.

However, that seems to have still caused problems for those that do dual-boot. Oops. There's been quite a few reports of people unable to boot into their Linux distributions as a result of this update. A potential solution can be found in an Ubuntu Discourse post from 2023 for a previous issue.

Microsoft haven't yet said anything about it that I can find, and their update page notes "Microsoft is not currently aware of any issues with this update", so clearly that needs an update.

Article taken from GamingOnLinux.com.
18 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
46 comments
Page: 1/5»
  Go to:

dpanter Aug 21
I'm sure we can trust M$ to never do something like this on purpose.
rambo919 Aug 21
Not for nothing that duel booting often ends up in an unbootable linux if you use UEFI the way it tells you to use it.... secure boot has always been more of a liability than a help.

It seems "legacy" boot is unaffected.
Haven't noticed anything. I think Secure Boot is disabled for me, so that's why.
QuoteMicrosoft haven't yet said anything about it that I can find, and their update page notes "Microsoft is not currently aware of any issues with this update", so clearly that needs an update.
Well..... Its not an "issue" if its planned is it???......
pb Aug 21
Ahh, good old evil microsoft, we didn't miss you.
Vardamir Aug 21
I have a simple rule: If you need Windows, install it in a VM. Never ever grant Windows access to real hardware.
elmapul Aug 21
that is why i dont dualboot anymore.
risk of sabotage, and they can claim it was an accident.
Claude_Lib Aug 21
I have Windows on a separate drive for rare occasions when I need it. The only clue two systems have about each other's existence is that Windows messes up the clock because I keep forgetting to set the RealTimeIsUniversal registry key.
soulsource Aug 21
Quoting: Claude_LibI have Windows on a separate drive for rare occasions when I need it. The only clue two systems have about each other's existence is that Windows messes up the clock because I keep forgetting to set the RealTimeIsUniversal registry key.
This update might break exactly such setups. The list of revoked keys is stored in an EFI variable (-> mainboard memory), and if Windows is unaware that there is a Linux installation, it will happily update that list - making Secure Boot prevent the execution of GRUB versions signed with the now-revoked keys.
Tchey Aug 21
I’m not DualBooting anymore, i got ride of this process maybe around seven years ago ? Last time was Win7, playing a few games, mostly MMORPG. Then never more.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.