alphacyberranger@sh.itjust.works to Programmer Humor@programming.devEnglish · 2 months agoMalware As A Servicesh.itjust.worksimagemessage-square23fedilinkarrow-up129arrow-down10
arrow-up129arrow-down1imageMalware As A Servicesh.itjust.worksalphacyberranger@sh.itjust.works to Programmer Humor@programming.devEnglish · 2 months agomessage-square23fedilink
minus-squareCornelius_Wangenheim@lemmy.worldlinkfedilinkarrow-up0·edit-22 months agoBecause it isn’t. Their Linux sensor also uses a kernel driver, which means they could have just as easily caused a looping kernel panic on every Linux device it’s installed on.
minus-squareYTG123@sopuli.xyzlinkfedilinkarrow-up0·2 months agoThere’s no way of knowing that, though. Perhaps their Linux and Darwin drivers wouldn’t have paniced the system? Regardless, doing almost anything at the kernel level is never a good idea
minus-squareohmyiv@lemmy.worldlinkfedilinkarrow-up0·2 months agoIt’s not impossible. Crowdstrike has done it recently to linux machines. 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
minus-squareMatch!!@pawb.sociallinkfedilinkEnglisharrow-up0arrow-down1·2 months agoPaywalled, unfortunately
Because it isn’t. Their Linux sensor also uses a kernel driver, which means they could have just as easily caused a looping kernel panic on every Linux device it’s installed on.
There’s no way of knowing that, though. Perhaps their Linux and Darwin drivers wouldn’t have paniced the system?
Regardless, doing almost anything at the kernel level is never a good idea
It’s not impossible. Crowdstrike has done it recently to linux machines.
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
Paywalled, unfortunately