Could you guys check whether the issue is still seen on 5.18.x kernel? It might be already fixed there.