This is amateur hour. For something so critical as a kernel module/driver, it would mean that code reviews failed, static analysis tools weren’t used, their DevOps pipeline and test suite failed to catch this, nobody ran any manual tests, etc..
So, at what point do you wonder about sabotage? If it isn’t, then it’s a very sorry state of affairs at MS. For a KERNEL MODULE!
Given the scale of this, I believe an investigation is warranted. I’d put money on sabotage.
Unfortunately, I got caught up in it - I had a two-week business trip with a flight home yesterday, I woke to the news of this issue and the problems banks & airlines were having. Typical! Of course my flight was delayed, then delayed, then delayed, with me finally getting home at 3:30am.
Sigh.
This was not a problem from Microsoft. It was a problem from the Crowd Strike company.
This was an organizational and management problem, not sabotage. They released an insufficiently tested version of their computer security product on their entire customer base at the same time. You never do that.
They won't do that again. Most likely they will go out of business and cannot do that again.
“If it isn’t, then it’s a very sorry state of affairs at MS”
This didn’t occur at MSFT.