Menu

Star on GitHub · 3.2k

CVE-2026-68092

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…

Published Aug 10, 2026EPSS 0.21%

Overview

CVE-2026-68092 is a known-severity vulnerability. It was published on August 10, 2026.

Technical description

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().

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-68092?

CVE-2026-68092 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68092?

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-68092?

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-68092?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68092 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.