time/jiffies: Register jiffies clocksource before usage
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().
- Published
- Aug 10, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.13affected
- 1a678f6829a8c931fae2b62e4c88dae743c839c9 and later · before fe9bdea65ba231fcfb155031628bb1e8491b5fe0affected · git
- 76031d9536a076bf023bedbdb1b4317fc801dd67 and later · before cd25e9819620aa1325897912cfb4dd89303325feaffected · git
- 76031d9536a076bf023bedbdb1b4317fc801dd67 and later · before 75b478096c6bbf57fe366f7f0a8cd5365043ffaaaffected · git
- 76031d9536a076bf023bedbdb1b4317fc801dd67 and later · before f24df84cbe05e4471c04ac4b921fc0340bbc7752affected · git
- 6.12.5 and later · before 6.12.97affected · semver
- before 6.13not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.39 and later · up to and including 6.18.*not affected · semver
- 7.1.4 and later · up to and including 7.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 6.12.97 | Vendor (CNA) |
| Linux Linux | 75b478096c6bbf57fe366f7f0a8cd5365043ffaa | Vendor (CNA) |
| Linux Linux | cd25e9819620aa1325897912cfb4dd89303325fe | Vendor (CNA) |
| Linux Linux | f24df84cbe05e4471c04ac4b921fc0340bbc7752 | Vendor (CNA) |
| Linux Linux | fe9bdea65ba231fcfb155031628bb1e8491b5fe0 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/75b478096c6bbf57fe366f7f0a8cd5365043ffaa
- git.kernel.org/stable/c/cd25e9819620aa1325897912cfb4dd89303325fe
- git.kernel.org/stable/c/f24df84cbe05e4471c04ac4b921fc0340bbc7752
- git.kernel.org/stable/c/fe9bdea65ba231fcfb155031628bb1e8491b5fe0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.