In the Linux kernel, the following vulnerability has been resolved: um: work around schedyield not yielding in time-travel mode schedyield by a userspace may not actually cause scheduling in time-travel mode as no time has passed. In the case seen it appears to be a badly implemented userspace spinlock in ASAN. Unfortunately, with time-travel it causes an extreme slowdown or even deadlock depending on the kernel configuration (CONFIGUMLMAXUSERSPACEITERATIONS). Work around it by accounting time to the process whenever it executes a sched_yield syscall.