The kernel backtrace looks to me like the one in bug #1206681. So maybe the problem is already fixed with kernel 6.1.8.