As for detection, Zach mentions that modern tooling could've been used to find this, so I'm assuming Valgrind can find this: https://x.com/Perpetualmaniac/status/1814376690958868979
Hope this helps!
So if I put this all together:
a) The driver (sensor) csagent.sys includes code that hasn't checked with a tool like Valgrind or ASan or something and so includes some kind of memory management bug.
b) Since n, n-1 and n-2 versions of the sensor all died equally spectacularly, that bug as been around for at least three versions of csagent.sys.
c) The bug can be triggered by getting the csagent.sys to swallow a shitty channel file and since csagent runs in kernel mode, when it crashes it BSOD's the system.
d) Someone at Crowdstrike uploaded a shitty channel file as part of an update process that apparently happens many times a day.
Am I on the right track so far? If so, there's no/inadequate memory management checks in the csagent driver, and either:
1)There were also no checks before the borked channel file was uploaded because of a failure to follow process, or because there was no process, but whatever the case it was an accident.
or
2) Someone uploaded on purpose, not by accident, the borked channel file intending for a nasty outcome (probably not BSOD)
I can't believe that there are not a million checks and balances in place to let (1) happen, but as my grandma used to say, "Don't assume malice where stupidity will do" :-)