So the issue persists for 8 months then corrects itself. The only thing I can think is that the software doesn't properly work with the 10 bit rollover of the GPS week number (which happens roughly every twenty years). Now we would expect to see this bug in 2019 when the week number went from 1023 to 0. Some clever programmer probably changed the epoch so that with a car sold in say 2010 that it handles the time correctly from 2004 up to 2029. So why the bug in 32 weeks of 2022? Well maybe some other clever programmer back in 2002 wrote some tests to check the handling with dates in 2002. Now with the 2010 update those tests fail as they say 2022 instead of 2002. Finally some naïve programmer writes a workaround to fix those failing tests so that if the week number matches the week number used in the tests it subtracts 1024 weeks such that the tests pass. After all 2022 looks like a long way ahead back in 2010!