Menu

Star on GitHub · 3.5k

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_…

Published Sep 11, 2026EPSS 0.21%

Overview

CVE-2026-80927 is a known-severity vulnerability. It was published on September 11, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80927?

CVE-2026-80927 is a known-severity vulnerability. It was published on September 11, 2026.

How severe is CVE-2026-80927?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80927?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80927?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80927 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach