I have just tested the kernel with the fix for bug #1181133 (kernel-default-5.10.9-1.1.g8b72572.x86_64) and I got the very same error. So it seems it is not a kernel bug.