Honda, Acura cars hit by Y2K22 bug that rolls back clocks to 2002

Honda and Acura cars have been hit with a Year 2022 bug, aka Y2K22, that resets the navigation system's clock to January 1st, 2002, with no way to change it.

Starting on January 1st, the date on Acura and Honda navigation system would automatically change to January 1st, 2002, with the time resetting to 12:00, 2:00, 4:00, or other times based on the model or possibly the region the car is located.

Honda and Acura car owners report that the Y2K22 bug affects almost all older cars, including Honda Pilot, Odyssey, CRV, Ridgeline, Odyssey and Acura MDX, RDX, CSX, and TL models.

Navigation clock resetting to January 1st, 2022
Source: Twitter

While it is unclear what is causing the Honda/Acura bug, this past weekend, Microsoft Exchange was hit by a Y2K22 bug that froze the delivery of email.

Microsoft's bug was caused by the date being stored in an int32 variable that can hold only a maximum value of 2,147,483,647. However, dates in 2022 have a minimum value of 2,201,010,001 for January 1st, 2022, at midnight, causing the software to crash.

The same bug may affect Honda and Acura cars, but Honda customer service has said it should resolve itself in August 2022, indicating it may be a different issue.

"Yes, we are so sorry for the issue you are experiencing with your vehicle. We have escalated the NAVI Clock Issue to our Engineering Team and they have informed us that you will experience issue from Jan 2022 thru August 2022 and then it will auto-correct," Honda customer support told a car owner.

Another Honda owner was given a similar response that the issue will automatically be fixed in August 2022.

"We're aware of the issue our engineers are looking into it. They've advised its something to do with the navi's calendar and that it will resolve itself when the date rolls over into August but they're looking for a counter measure to correct it sooner," customer support told another owner.

It is doubtful that Acura and Honda will force a car owner to wait seven months for a fix, and an update for the navigation system will likely be released to resolve the issue.

BleepingComputer has reached out to Acura and Honda to learn more about the bug and how they plan on fixing it but have not heard back.

Thx Aristides for the tip!