Just for the sake of narrowing the bug down, I can confirm that if I boot into the 5.19.0 kernel, without changing anything else, the bug does not occur.