# CVE-2026-68092: time/jiffies: Register jiffies clocksource before usage

> A Linux kernel bug causes boot delays in XEN HVMs by clamping time progress, resulting in a denial of service during system startup.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68092, DEBIAN-CVE-2026-68092, GHSA-x4mh-q3jq-rwpp, UBUNTU-CVE-2026-68092

## What is CVE-2026-68092?

CVE-2026-68092 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-68092?


## How do I fix CVE-2026-68092?

Apply the vendor's patch.

## Is CVE-2026-68092 being exploited?

There is no known exploitation of CVE-2026-68092 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68092 and fix it if it is affected.

What it is: CVE-2026-68092 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68092 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68092/ (Markdown: https://insights.sbomify.com/CVE-2026-68092/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68092
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68092
- OSV: https://osv.dev/vulnerability/CVE-2026-68092

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68092/
Summaries are generated and may contain mistakes; the official description above is the record.