um: work around sched_yield not yielding in time-travel mode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In Linux kernel time-travel mode, a userspace sched_yield call may not trigger scheduling because no time has passed. A local process using sched_yield can cause extreme slowdown or deadlock, depending on the CONFIG_UML_MAX_USERSPACE_ITERATIONS setting; no authentication or user interaction requirements are specified.
Engineers running Linux kernels in UML time-travel mode should check their installations; affected versions were not provided.