time/jiffies: Register jiffies clocksource before usage
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:
time/jiffies: Register jiffies clocksource before usage
Teddy reported that a XEN HVM has a long boot delay, which was bisected to the recent enhancements to the negative motion detection. It turned out that the jiffies clocksource is used in early boot before it is registered, which leaves the max_delta_raw field at zero. That causes the read out to be clamped to the max delta of 0, which means time is not making progress.
Cure it by ensuring that it is initialized before its first usage in timekeeping_init().
From the CVE record · Linux
The Linux kernel can use the jiffies clocksource during early boot before it is registered, causing time to stop progressing. This was reported as a long boot delay on a Xen HVM system; the input describes no attacker action, authentication requirement, or user interaction.
Engineers running Linux kernels on Xen HVM systems should check whether their kernel is affected; affected versions are not specified.