In other words, "content dispute" locks are now freezing questions instead of locking them.
Per the second link above, locks on questions for reasons other than "historical significance" and "obsolete" are supposed to only disallow interactions with the question while the answers remain unlocked and interactable. This question was locked with the "content dispute" reason before this bug came up, and it is working as designed there.
However, it appears that the behavior meant only for "historical" and "obsolete" locks is now applying to questions locked as "content disputes": the answers are being locked and the vote buttons are being hidden on the question and all answers (even though the latter should still be able to be voted on with this type of lock):
This doesn't seem to happen for "wiki answer" locks (which are meant to impose identical restrictions as "content dispute" locks); it only happens for "content dispute" locks.
Can this please be fixed? I think this may have happened because the menu was programmed to impose this type of lock on specific indexes in the locking menu, and the order was changed and indexes weren't updated to reflect the change.