um: time-travel: fix time corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
um: time-travel: fix time corruption
In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding.
Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.
From the CVE record · Linux
In basic UML time-travel mode, a timer interrupt can occur while the kernel is advancing time, causing time to move backwards and the kernel to crash. The input does not establish whether an attacker can trigger this condition or specify any network, authentication, or user-interaction requirements.
Engineers running the Linux kernel with basic UML time-travel mode should check their installations; affected versions are not specified.