Update: I just encountered the same issue on the 5.3.18-59.16 kernel. It seems less frequent there, though.