It is possible that some script that runs during update sends SIGINT to the wrong process by mistake. Try to analyze what packages were updated when this happened.
Oh, false alarm. This time something went wrong with initrd creation during update. I mean it’s still bad, but not the issue I described. I too quickly just assumed it happened, before actually checking it.
Case closed for now. I’ll get back to it if it ever happens again.