CVE-2025-37880
um: work around sched_yield not yielding in time-travel mode
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
um: work around sched_yield not yielding in time-travel mode
In the Linux kernel, the following vulnerability has been resolved: um: work around sched_yield not yielding in time-travel mode sched_yield 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 (CONFIG_UML_MAX_USERSPACE_ITERATIONS). Work around it by accounting time to the process whenever it executes a sched_yield syscall.
Reserved 2025-04-16 | Published 2025-05-09 | Updated 2025-05-09 | Assigner Linuxgit.kernel.org/...c/da780c4a075ba2deb05ae29f0af4a990578c7901
git.kernel.org/...c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2
git.kernel.org/...c/887c5c12e80c8424bd471122d2e8b6b462e12874
Support options
