timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()
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 |
|
|
6.18.507.2.47.3In the Linux kernel, the following vulnerability has been resolved:
timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()
If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled before tks->clock_valid is checked, then uninitialized stackdata will be used in the calculations and indirectly leaked to userspace.
The same race window also exists after this change and also for the core timekeeper. But in these cases the only effect would be incorrect adjustments and this is userspace's responsibility to avoid this.
From the CVE record · Linux
A race in the Linux kernel’s timekeeping code can use uninitialized stack data in calculations and indirectly leak it to userspace. This can occur when the auxiliary clock is disabled during tk_get_aux_ts64() and re-enabled before the clock-validity check.
Teams running the Linux kernel should check their installations; affected versions were not specified.