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.
Product status
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 887c5c12e80c8424bd471122d2e8b6b462e12874
6.14.5 (semver)
6.15 (original_commit_for_fix)
References
git.kernel.org/...c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2
git.kernel.org/...c/887c5c12e80c8424bd471122d2e8b6b462e12874
