First published: Fri May 09 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-37880 is considered a medium severity vulnerability due to its impact on scheduling in time-travel mode.
To fix CVE-2025-37880, users should update to the latest version of the Linux kernel that addresses this vulnerability.
CVE-2025-37880 affects systems running the affected Linux kernel versions that utilize time-travel mode.
The impact of CVE-2025-37880 may lead to improper scheduling behavior, potentially affecting system performance and responsiveness.
CVE-2025-37880 is not remotely exploitable as it requires user space interaction for the sched_yield function.