System disruption via wrong timekeeper leap-state update
Published Feb 4, 2026 · Updated Feb 4, 2026
Timekeeping flaw in Linux Kernel 6.17 through 6.18.7 and 6.19-rc1 through 6.19-rc6 allows local users to disrupt system availability. In __do_ajdtimex(), an auxiliary-clock request updates the global tk_core leap state instead of the selected timekeeper, writing its sequence lock without the matching spinlock. Triggering the faulty write requires an adjustable auxiliary clock and CAP_SYS_TIME, and the documented consequence is incorrect core timekeeping with a lock-debugging warning.
Summary
What happened
Timekeeping flaw in Linux Kernel 6.17 through 6.18.7 and 6.19-rc1 through 6.19-rc6 allows local users to disrupt system availability. In __do_ajdtimex(), an auxiliary-clock request updates the global tk_core leap state instead of the selected timekeeper, writing its sequence lock without the matching spinlock. Triggering the faulty write requires an adjustable auxiliary clock and CAP_SYS_TIME, and the documented consequence is incorrect core timekeeping with a lock-debugging warning.
The record
- CVE
- CVE-2026-23106
- Published
- Feb 4, 2026
- Updated
- Feb 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 4, 2026CVE publishedPublication date reported by the CVE source.
- Feb 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.17
- Affected versionversion=775f71ebedd382da390dc16a4c28cffa5b937f79 <8f7c9dbeaa0be5810e44d323735967d3dba9239d
- Affected versionversion=775f71ebedd382da390dc16a4c28cffa5b937f79 <e806f7dde8ba28bc72a7a0898589cac79f6362ac
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo