Strix
63.2K

CVE-2026-80927

Unknown

Last modified

CVE-2026-80927 is a vulnerability of currently unknown severity. 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..

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4eca49d0b621b314ac7c80f363932ec6f6c8abc8, < fecf1e37775269ad38c172b468ad4ecc3968aa63; >= 4eca49d0b621b314ac7c80f363932ec6f6c8abc8, < bc59dac50cb45a725f7a50760c7cc72a0964f722; >= 4eca49d0b621b314ac7c80f363932ec6f6c8abc8, < 4b61084b11bcecce86d03804ff30f8d7b465593c
LinuxLinux6.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80927?
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.
How severe is CVE-2026-80927?
Severity scoring for CVE-2026-80927 is pending analysis.
How do I fix CVE-2026-80927?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80927?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST