If an engineer builds a bridge and it falls down, s/he will get punished for it.
If a doctor or a lawyer makes a similar hard mistake, s/he will get punished for it.
The same needs to happen to software engineering, specially given that in most countries software engineering is a degree with the respective Engineering Order.
For example, we can't hold Linus Torvalds liable when the Linux Kernel has a bug (perhaps not even if it was deliberate!). If we even tried to, the entire project would likely come to a screeching halt.
How is this model of liability compatible with large open source codebases?
Yes, like in other fields. Obviously people are not chased out of town for as small error.
It's when people conspire together to hide big problems that liability becomes important.
And frankly, if your thermostat malfunctions and runs your heat full bore for a weekend while you're out of town, I don't think it's unreasonable to say that, assuming basic requirements were present for functionality (power, connectivity to the furnace, etc.) that the company should be responsible if their system went wrong solely because of poorly designed software. If for nothing else than your outrageous heating bill.
And again, if a company's response is "well we don't want to be responsible for your furnace" then my response is "then don't be making fraking thermostats, because that's what they're FOR!"
So I would agree that in this hypothetical case, the IoT company needs a custom kernel patch on their device, and hopefully it gets upstreamed.
But if all this occurs after your furnace is shot, you're left asking the manufacturer, "Why did you use Linux at all in this product?" You would think they'd then accept responsibility but what if they do try to blame the Linux project and have expensive lawyers to back them up?
This all seems to add up to a potential spaghetti mess of blame where the legal model is "doctors and lawyers and bridge builders." In fact I think these problems need to be addressed outside current legal and regulatory systems which frankly can't keep up with the pace of open source software.
In a cell phone? Sure, because the replacement process is a somewhat annoying sales appointment at $carrier. In a thermostat? No, because it should last years. Maybe decades if it's a good one. IoT falls apart in this arena because the hardware is designed to be replaced often, and that's exactly what house hardware should not be.
And if the software is too complex, then don't do it. Do it right or don't bother.
The idea being that these patching companies would become recognised brands, and the manufacturer would get to put a "Supported by FooCorp until 2031" badge on their packaging, and consumers would start to expect to see this.
No, maybe you won't be able to set it up with a smartphone and 2 minutes, but it also might WORK BETTER if it wasn't able to do that.
Also, even if manufacturers are held to account more, we will still see severe bugs, IMO, in Linux or even some hypothetically more secure, future OS.
As it's framed in this article at least, I think the automotive manufacturer metaphor falls down at some point (even if most cars now run Linux too). I think software is just vastly more complex and we are just now learning how to cope with that complexity.