Indeed, the problem is no longer reproducible with recent kernels (e.g., 6.11.8). Sorry for not having reported back on this to close the bug.