Home

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.

PUBLISHED Reserved 2025-04-16 | Published 2025-05-09 | Updated 2026-05-11 | Assigner Linux

Product status

Default status
unaffected

065038706f77a56754e8f0c2556dab7e22dfe577 (git) before 990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2
affected

065038706f77a56754e8f0c2556dab7e22dfe577 (git) before 887c5c12e80c8424bd471122d2e8b6b462e12874
affected

Default status
affected

5.3
affected

Any version before 5.3
unaffected

6.14.5 (semver)
unaffected

6.15 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2

git.kernel.org/...c/887c5c12e80c8424bd471122d2e8b6b462e12874

cve.org (CVE-2025-37880)

nvd.nist.gov (CVE-2025-37880)

Download JSON