Two Chips Fought Over a Memory Address. 20,991 EVs Can Lose Power at Highway Speed.

Let me tell you about the dumbest possible way to make a car stop working. Inside the battery ECU of the 2026 Toyota bZ, Lexus RZ, and Subaru Solterra sits a pair of integrated circuits: one monitors the battery, the other controls it, and both write to the same memory address. When their write cycles collide, the stored data corrupts, the ECU fails its own self-check, and the entire electric drive system shuts down at whatever speed you happen to be traveling.^[1]

This is a race condition, the kind of concurrency bug computer science students learn to avoid in their second semester. You fix it with a lock, a semaphore, a mutex. Dijkstra published the solution in 1965, and sixty-one years later a production vehicle shipped without it.

Toyota discovered the bug while testing firmware for an unrelated plug-in hybrid in development.^[2] Engineers noticed abnormal write cycling on certain EV platforms, ran targeted tests in April 2026, and confirmed the cascade: corrupted memory, malfunction indicators across multiple systems, then total loss of drive power. Steering and brakes retain hydraulic assist, so you can coast to the shoulder if you have a shoulder and the composure to use it.

One warranty claim exists that may relate to this defect. Nobody has crashed, nobody has died, and Toyota caught this before the body count started, which matters, but the failure class matters more.

Our FARS dataset puts the newest EVs at the bottom of the death-rate rankings: the Tesla Model Y at 0.03 fatalities per 100 million VMT, the Model 3 at 0.05.^[3] Those numbers reflect crash avoidance and structural engineering. What they do not reflect is firmware reliability, because FARS counts bodies after metal bends, not the software fault that made it bend.

The aerospace industry solved this decades ago; DO-178C requires formal verification that would flag a shared-memory write conflict before the code compiled for production hardware.^[4] ISO 26262, the automotive equivalent, prescribes testing but does not mandate those techniques. The gap between those standards is the gap between an industry that assumes its software will kill someone and an industry still getting used to the idea.

Every recalled vehicle needs a dealer-applied ECU software update; no over-the-air fix is available because bricking a battery ECU over a cell connection is the kind of second-order failure nobody wants to explain in the next recall filing.^[2]

What you should do with this: If you own a 2026 Toyota bZ, Lexus RZ, or Subaru Solterra, NHTSA recall 26V393000 covers your vehicle. Search your VIN at nhtsa.gov/recalls and schedule the dealer update before your next highway trip. If you are shopping for any EV, understand that failure modes have migrated: the thing that kills your drive power is no longer a broken fuel pump but two chips writing to the same address at the same time.