The cause is a malfunction of the Crowdstrike monitoring solution, which employees use to spy at anything ever done on company hardware. They do have a Linux version and it has been reported to cause kernel panics (not sure if during this incident).

[–] Dudewitbow@lemmy.zip 0 points 4 months ago

it was because crowdstrike themselves notified that this specific instance did not affect their linux nor osx distributions of security, and was windows specific.

[–] ohmyiv@lemmy.world 0 points 4 months ago* (last edited 4 months ago)

This in particular is a Crowdstrike issue. They suck as much as windows. Crowdstrike has had issues on Linux before:

Crowdstrike - freezing RockyLinux After 9.4 upgrade:: https://forums.rockylinux.org/t/crowdstrike-freezing-rockylinux-after-9-4-upgrade/14041

Kernel panic observed after booting 5.14.0-427.13.1.el9_4.x86_64 by falcon-sensor process:
https://access.redhat.com/solutions/7068083

Debian user experience: https://news.ycombinator.com/item?id=41005936

Another windows story: https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/

[–] CalcProgrammer1@lemmy.ml 0 points 4 months ago (2 children)

Should have not trusted a third party to install proprietary code into the kernel. It's not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.

[–] Damage@slrpnk.net 0 points 4 months ago (3 children)

They have a Linux version, but this happened only to the Windows one... Coincidence?!

[–] qjkxbmwvz@startrek.website 0 points 4 months ago (1 children)

Probably coincidence? It sounds (???) like this is a pretty simple fix on Windows.

The number of times I have borked my Linux machines so they wouldn't boot is, well, greater than zero for sure. Any operating system can be bricked to the point of requiring manual intervention by software with elevated privileges.

[–] Rentlar@lemmy.ca 0 points 4 months ago

The simple fix: turn it off and on up to 15 times

The simple fix 2: delete system32

[–] pearsaltchocolatebar@discuss.online 0 points 4 months ago

It's not like they haven't caused Linux outages in the past.

[–] CalcProgrammer1@lemmy.ml 0 points 4 months ago

Yes, coincidence.

[–] SatansMaggotyCumFart@lemmy.world 0 points 4 months ago (1 children)

Counterpoint: Windows bad.

[–] CalcProgrammer1@lemmy.ml 0 points 4 months ago

I can't disagree with you there.