I don't think this a regression, or a problem is related to this update at all. I've seen it a few times before, in much older releases than this. Could be triggered by a GPS module restart or something during update.
Occasional inaccuracies are assumed, you can get that with reflections and weak signal, I've seen that before. But this was basically offset an exact amount in one direction, and didn't fix itself over the course of a 30 mile drive over 45 minutes, including a reboot. This is just broken. It should have fixed itself within seconds of getting a good GPS fix.