Linux needs to come in after the fact and run on whatever garbage happened to ship.
(FWIW: in this case the root cause was a host bridge in the tables which had been granted a truly outrageous memory space despite having no devices in it. It was likely a typo, or some test stuff that got left in.)
I was not writing code at the time and had nothing to contribute.
So apparently they fixed it later.... then came the security issues, unexpected behavior, shit going sideways.
Sometimes a straight crash is not such a bad thing.
One of the things I like about Kubernetes is that the ecosystem (generally) tries to adhere to the "Not healthy? Then crash and keep crashing" mantra when something doesn't work. If I see something is in a CrashLoopBackoff I at least know its b0rked. Stuff that reports its up and running when it's actually hosed is really annoying.
The worst sort of thing to track down is working ... but not. God knows when it started or what it has impacted.
Worse if it impacts real data or data goes where it shouldn't.
You're assuming this was an issue. Manufacturers religiously create artificial tiers in software to upsell users. This is true of hardware just as much as it is software.