CVE-2025-37880: Linux kernel · um: work around sched_yield not yielding in time-travel mode
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 12 Nov 2026, 20:05 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2025-37880 (opens in a new tab)
- git.kernel.org/stable/c/887c5c12e80c8424bd471122d2e8b6b462e12874 (opens in a new tab)
- git.kernel.org/stable/c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2 (opens in a new tab)
- git.kernel.org/stable/c/da780c4a075ba2deb05ae29f0af4a990578c7901 (opens in a new tab)