Skip Navigation

“Something has gone seriously wrong,” dual-boot systems warn after Microsoft update

Last Tuesday, loads of Linux users—many running packages released as early as this year—started reporting their devices were failing to boot. Instead, they received a cryptic error message that included the phrase: “Something has gone seriously wrong.”

The cause: an update Microsoft issued as part of its monthly patch release. It was intended to close a 2-year-old vulnerability in GRUB, an open source boot loader used to start up many Linux devices. The vulnerability, with a severity rating of 8.6 out of 10, made it possible for hackers to bypass secure boot, the industry standard for ensuring that devices running Windows or other operating systems don’t load malicious firmware or software during the bootup process. CVE-2022-2601 was discovered in 2022, but for unclear reasons, Microsoft patched it only last Tuesday.

...

The reports indicate that multiple distributions, including Debian, Ubuntu, Linux Mint, Zorin OS, Puppy Linux, are all affected. Microsoft has yet to acknowledge the error publicly, explain how it wasn’t detected during testing, or provide technical guidance to those affected. Company representatives didn’t respond to an email seeking answers.

168 comments
  • Secure Boot is bullshit anyway

    • It is fine if you only accept signatures from yourself. However, that's a lot of work as you need to sign everything.

      • Good luck replacing the PKI on your system's Secure Boot firmware. Most platforms probably don't support it and have no documentation

      • How is it a lot of work? There's generally one sig you have to add on installing a new OS. Sometimes, rarely, one for a new kernel module. It's not like you sign every single package you boot.

  • “The SBAT value is not applied to dual-boot systems that boot both Windows and Linux and should not affect these systems,” the bulletin read. “You might find that older Linux distribution ISOs will not boot. If this occurs, work with your Linux vendor to get an update.”

    Excuse me, those are the opposite of each other.

  • CVE-2022-2601 was discovered in 2022, but for unclear reasons, Microsoft patched it only last Tuesday.

168 comments