this post was submitted on 21 Aug 2024
629 points (99.1% liked)

Linux

48340 readers
383 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r
629
“Something has gone seriously wrong,” dual-boot systems warn after Microsoft update (arstechnica.com)
submitted 3 months ago by pnutzh4x0r@lemmy.ndlug.org to c/linux@lemmy.ml
169 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Wispy2891@lemmy.world 38 points 3 months ago (3 children)

If it's a Linux problem why Microsoft has to patch it?

It's like if someone gives you a ride to the hospital and the doctor treats him instead of you

[–] my_hat_stinks@programming.dev 24 points 3 months ago (1 children)

I'm not sure I follow that analogy, if you get a ride to a hospital you don't expect it to lock off all other destinations. What happens in the hospital is irrelevant.

From reading the article, this is more like if you walk into a hotel and they burn down your house so you have no choice but to stay. I suppose in theory you could argue in very bad faith that this is a problem with the house since it's the house that burned, but in reality the problem is the fact they're the ones who started the fire.

[–] chautalees@lemmy.world 11 points 3 months ago

We didn't start the fire, it was always burning since the World's been turning

[–] endofline@lemmy.ca 21 points 3 months ago (1 children)

Because people cannot block darn windows updates. Its a real malware only allowed by law

[–] possiblylinux127@lemmy.zip 18 points 3 months ago

Microsoft: you can have security updates

Users: good

Microsoft: just keep in mind they will make major changes and will totally change the desktop and settings.

Users: wait what Microsoft Edge opens

[–] chameleon@fedia.io 4 points 3 months ago

It's a problem in the Secure Boot chain, every system is affected by any vulnerability in any past, present or future bootloader that that system currently trusts. Even if it's an OS you aren't using, an attacker could "just" install that vulnerable bootloader.

That said, MS had also been patching their own CVE-2023-24932 / CVE-2024-38058, and disabled the fix for that in this update due to widespread issues with it. I don't think anyone knows what they're doing anymore.