timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4eca49d0b621b314ac7c80f363932ec6f6c8abc8 · fixed in fecf1e37775269ad38c172b468ad4ecc3968aa63; From 4eca49d0b621b314ac7c80f363932ec6f6c8abc8 · fixed in bc59dac50cb45a725f7a50760c7cc72a0964f722; From 4eca49d0b621b314ac7c80f363932ec6f6c8abc8 · fixed in 4b61084b11bcecce86d03804ff30f8d7b465593c
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4