YOU need to read up on stuxnet. It was literally half a dozen zero day vulnerabilities and the governments of 2 maybe 3 powerful nations that had to work on it to make something break, INTENTIONALLY. And it didn't break by some "glitch" it required a precise program that used the actual software of Siemens PLC's to do the damage.

It silenced alarms and spun the centrifuges up slowly so as to not create attention but it did so USING THE CONTROLS IN THE SYSTEM.

There were no "faulty drivers" when it came to stuxnet. It required actually very precise control and deliberate programming.

It also worked by deactivating the virus after several failed jumps wihtout finding the target to limit it's chance of being detected until AFTER it had done the damage. Which is why it took months for someone outside of Iran to actually find and discover it.

It was also completely harmless to anything OTHER than the primary target systems.

I did my senior thesis on it when I was a computer science major 10 years ago.

If there's an issue in this case it's shitty firmware that allows control of things beyond scope of intended use. i.e. it allows over voltage or some other factor that damages capacitors or other heat sensitive parts.

If plugging in an OBD2 reading into my car causes my engine to redline that's a design flaw in my car. If the OBD2 reader allows me to bypass safety margins WILLINGLY that's a user error if it breaks.

But simply connecting = damage it means they were sloppy and did a half ass job IMO.