Conversation
Notices
-
Embed this notice
nekobit (neko@clubcyberia.co)'s status on Saturday, 20-Jul-2024 07:10:53 JST nekobit Whats the actual cause of the kernel panic? (besides just "a buggy driver") - Sick Sun repeated this.
-
Embed this notice
Sick Sun (sun@shitposter.world)'s status on Saturday, 20-Jul-2024 07:10:53 JST Sick Sun @neko cc: @feld werent you talking about this -
Embed this notice
cool_boy_mew (coolboymew@shitposter.world)'s status on Saturday, 20-Jul-2024 07:40:38 JST cool_boy_mew @neko You've misread it, it's a kernel picnic, and Yogi Bear was there to steal everyone's lunch -
Embed this notice
feld (feld@bikeshed.party)'s status on Saturday, 20-Jul-2024 07:41:56 JST feld @sun @neko
PAGE_FAULT_IN_NONPAGED_AREASick Sun likes this. -
Embed this notice
翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 21-Jul-2024 04:00:40 JST 翠星石 @neko Pretty much ClownStrike doesn't do any testing on their patches and send out a dodgy "threat signature" file to almost all of the windows computers that are part of their botnet.
They have a windows kernel module written in sepples, which parses "threat signature" files with a ".sys" extension and applies them and someone went and tested in production by pushing one or more corrupted "threat signature" file(s), which caused the parser to de-reference a null-pointer and caused the NT kernel to crash.
I do wonder if de-referencing a NULL pointer in a Linux module will cause it to crash - I guess I better try it out.
https://www.crowdstrike.com/blog/falcon-update-for-windows-hosts-technical-details/ (do not run the JavaScript on the page - it is all useless malware that doesn't do anything useful).