CVE-2026-23106
Last modified
CVE-2026-23106 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: timekeeping: Adjust the leap state for the correct auxiliary timekeeper When __do_ajdtimex() was introduced to handle adjtimex for any timekeeper, this reference to tk_core was not updated. When called on an auxiliary timekeeper, the core timekeeper would be updated incorrectly. This gets caught by the lock debugging diagnostics because the timekeepers sequence lock gets written to without holding its associated spinlock: WARNING: include/linux/seqlock.h:226 at __do_adjtimex+0x394/0x3b0, CPU#2: test/125 aux_clock_adj (kernel/time/timekeeping.c:2979) __do_sys_clock_adjtime (kernel/time/posix-timers.c:1161 kernel/time/posix-timers.c:1173) do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131) Update the correct auxiliary timekeeper.. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: timekeeping: Adjust the leap state for the correct auxiliary timekeeper When __do_ajdtimex() was introduced to handle adjtimex for any timekeeper, this reference to tk_core was not updated. When called on an auxiliary timekeeper, the core timekeeper would be updated incorrectly. This gets caught by the lock debugging diagnostics because the timekeepers sequence lock gets written to without holding its associated spinlock: WARNING: include/linux/seqlock.h:226 at __do_adjtimex+0x394/0x3b0, CPU#2: test/125 aux_clock_adj (kernel/time/timekeeping.c:2979) __do_sys_clock_adjtime (kernel/time/posix-timers.c:1161 kernel/time/posix-timers.c:1173) do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131) Update the correct auxiliary timekeeper.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17, < 6.18.8 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23106?
How severe is CVE-2026-23106?
How do I fix CVE-2026-23106?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23101In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23102In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23103In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23104In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23105In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23107In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23108In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23109In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2311IBM i 7.6, 7.5, 7.4, 7.3, and 7.2 s vulnerable to privilege …9.8
- CVE-2026-23110In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23111In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-23106?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
