Bug 2513138 (CVE-2026-68092)

Summary: CVE-2026-68092 kernel: time/jiffies: Register jiffies clocksource before usage
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's time/jiffies clocksource. During early boot, the jiffies clocksource is used before it is properly registered, causing its maximum delta value to remain at zero. This issue prevents the system's time from progressing, leading to a significant boot delay, particularly observed in Xen Hardware Virtual Machine (HVM) environments.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-10 12:02:04 UTC 
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().
Comment 1 gkamathe 2026-08-11 10:07:25 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081000-CVE-2026-68092-85cd@gregkh/T