Hum
Software is a goods (that sounds awful). There are services around the goods such as maintenance, installation etc. but the delivered software is most definitely a goods. It does have a physical instantiation, it does have set of delivered features, it must deliver on those expectations. The instantiation is the material that it is delivered upon. In ancient times that might be a tape or a disc but nowadays it's more likely to be a download, which is instantiated on the receiving device. The set of features is the definition of what the software is expected to do. The expectation is that it delivers those features correctly and without prejudice.
The rules that apply to goods apply to software, it's just that most don't seem to know or care. Mostly the problems around fitness for purpose stem from a lack of clear definitions or changing expectations. We have been bludgeoned over the years into accepting very poor quality software. Free software has also muddied the waters and lowered expectations. To use your example of cars. There are well defined systems for recalling cars to fix defects that have caused the delivered goods (the car) from not performing to either the expected specification or to regulation. This includes the software components of the car as well as the more physical components. Such pathways should also be available for software only goods.
We just live with poor software and throw our collective hands up as if saying. "it's all far too complicated" and "what do you expect". Well, how about expecting well engineered software that correctly deals with the complexity. Oh, you would probably have to pay for it but who expects a free car?
/EndRant