LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23106: timekeeping: Adjust the leap state for the correct auxiliary timekeeper

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects timekeeping logic. When adjusting an auxiliary timekeeper, the kernel could update the main timekeeper incorrectly and trigger lock-debugging warnings. The sources do not describe business impact, exploitability, privilege requirements, or data exposure.

Executive priority

Track and remediate through normal Linux kernel patch management until vendor severity is known. Escalate only if your vendor assigns higher severity or confirms practical exploitation conditions.

Technical view

The bug is in __do_adjtimex handling for auxiliary timekeepers. A reference to tk_core was not updated, so the wrong timekeeper state could be modified, including leap-state handling. Lock debugging reports a sequence-lock write without the associated spinlock. Stable kernel commits correct the target timekeeper.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or affected commit ranges. The source bundle identifies Linux kernel 6.17, 6.18.8, and 6.19-related version data, but exact fleet impact requires checking distribution kernel advisories.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The sources show a syscall path involving clock_adjtime, but do not state whether the issue is reachable by unprivileged users or remotely exploitable.

Researcher notes

The strongest evidence is the upstream kernel resolution text and two stable commit references. Missing data includes CVSS, CWE, privilege requirement, practical impact, and distribution-specific affected ranges. Avoid extrapolating beyond kernel timekeeping corruption and lock diagnostics.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2026-23106.
  • Upgrade to a kernel containing the referenced stable fixes.
  • Prioritize systems using affected upstream kernel branches.
  • Do not assume impact without matching your vendor kernel build.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare vendor kernel changelogs against the referenced stable commits.
  • Check kernel logs for related seqlock or timekeeping warnings.
  • Confirm whether auxiliary timekeeper paths are present in deployed kernels.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23106 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux775f71ebedd382da390dc16a4c28cffa5b937f79, 775f71ebedd382da390dc16a4c28cffa5b937f79unaffected
LinuxLinux6.17, 0, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.