Holy shit!
Vehicle tests confirmed that one particular dead task would result in loss of throttle control, and that the driver might have to fully remove their foot from the brake during an unintended acceleration event before being able to end the unwanted acceleration.
From what I remember a bug that affected some Toyota ECUs related to the cruise control handling. The cruise control loop would read some global state variable for engine speed and gearbox selection to determine vehicle speed. The problem was, if you crashed the sensor loop that measured engine rpm, it was possible the cruise control loop could over-run on its acceleration. It's pretty easy to see if the cruise control is at 70 mph, but vehicle is at 69.5 mph, it might add 1% to the vehicle throttle. If the sensor doesn't update the data, then it will continue to add to the vehicle throttle until it hits its authority limit.
The authority limit will vary, on simpler control systems it will be just be fixed, but on more advanced systems it will use the gearbox angle sensor to provide better response, so if going uphill it will allow more power to be mixed in more quickly. So this sensor also becomes important because if the data from that goes awry then the cruise control could be allowed to use full power on even downhill slopes. Worst case the bit flips just as you crest a hill, cruise control has full power authority, and you're going down the hill with throttle heading towards 100%.
According to the report I read, there's absolutely no 'stale data' handling, in any of the cruise control logic. And this is not the only fatal design flaw in the software.