um: work around sched_yield not yielding in time-travel mode
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 887c5c12e80c8424bd471122d2e8b6b462e12874 and Kernel 990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.3, >=065038706f77a56754e8f0c2556dab7e22dfe577 <887c5c12e80c8424bd471122d2e8b6b462e12874, >=065038706f77a56754e8f0c2556dab7e22dfe577 <990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2 | 887c5c12e80c8424bd471122d2e8b6b462e12874, 990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket