Vulnerability-Lookup

GHSA-GX3F-MW8M-6FF3

Vulnerability from github – Published: 2026-02-04 18:30 – Updated: 2026-02-04 18:30

Details

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.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-23106"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-02-04T17:16:21Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntimekeeping: Adjust the leap state for the correct auxiliary timekeeper\n\nWhen __do_ajdtimex() was introduced to handle adjtimex for any\ntimekeeper, this reference to tk_core was not updated. When called on an\nauxiliary timekeeper, the core timekeeper would be updated incorrectly.\n\nThis gets caught by the lock debugging diagnostics because the\ntimekeepers sequence lock gets written to without holding its\nassociated spinlock:\n\nWARNING: include/linux/seqlock.h:226 at __do_adjtimex+0x394/0x3b0, CPU#2: test/125\naux_clock_adj (kernel/time/timekeeping.c:2979)\n__do_sys_clock_adjtime (kernel/time/posix-timers.c:1161 kernel/time/posix-timers.c:1173)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nUpdate the correct auxiliary timekeeper.",
  "id": "GHSA-gx3f-mw8m-6ff3",
  "modified": "2026-02-04T18:30:44Z",
  "published": "2026-02-04T18:30:44Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23106"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8f7c9dbeaa0be5810e44d323735967d3dba9239d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e806f7dde8ba28bc72a7a0898589cac79f6362ac"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-23106 (GCVE-0-2026-23106)

Vulnerability from cvelistv5 – Published: 2026-02-04 16:08 – Updated: 2026-02-04 16:08

Title

timekeeping: Adjust the leap state for the correct auxiliary timekeeper

Summary

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.

Severity ?

No CVSS data available.

Assigner

Linux

References

URL

Tags

	https://git.kernel.org/stable/c/8f7c9dbeaa0be5810…
	https://git.kernel.org/stable/c/e806f7dde8ba28bc7…

Impacted products

Vendor

Product

Version

Linux

Affected: 775f71ebedd382da390dc16a4c28cffa5b937f79 , < 8f7c9dbeaa0be5810e44d323735967d3dba9239d (git)
Affected: 775f71ebedd382da390dc16a4c28cffa5b937f79 , < e806f7dde8ba28bc72a7a0898589cac79f6362ac (git)

Linux

Affected: 6.17
Unaffected: 0 , < 6.17 (semver)
Unaffected: 6.18.8 , ≤ 6.18.* (semver)
Unaffected: 6.19-rc7 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/time/timekeeping.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "8f7c9dbeaa0be5810e44d323735967d3dba9239d",
              "status": "affected",
              "version": "775f71ebedd382da390dc16a4c28cffa5b937f79",
              "versionType": "git"
            },
            {
              "lessThan": "e806f7dde8ba28bc72a7a0898589cac79f6362ac",
              "status": "affected",
              "version": "775f71ebedd382da390dc16a4c28cffa5b937f79",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/time/timekeeping.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19-rc7",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.8",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19-rc7",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntimekeeping: Adjust the leap state for the correct auxiliary timekeeper\n\nWhen __do_ajdtimex() was introduced to handle adjtimex for any\ntimekeeper, this reference to tk_core was not updated. When called on an\nauxiliary timekeeper, the core timekeeper would be updated incorrectly.\n\nThis gets caught by the lock debugging diagnostics because the\ntimekeepers sequence lock gets written to without holding its\nassociated spinlock:\n\nWARNING: include/linux/seqlock.h:226 at __do_adjtimex+0x394/0x3b0, CPU#2: test/125\naux_clock_adj (kernel/time/timekeeping.c:2979)\n__do_sys_clock_adjtime (kernel/time/posix-timers.c:1161 kernel/time/posix-timers.c:1173)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nUpdate the correct auxiliary timekeeper."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-02-04T16:08:27.046Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/8f7c9dbeaa0be5810e44d323735967d3dba9239d"
        },
        {
          "url": "https://git.kernel.org/stable/c/e806f7dde8ba28bc72a7a0898589cac79f6362ac"
        }
      ],
      "title": "timekeeping: Adjust the leap state for the correct auxiliary timekeeper",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23106",
    "datePublished": "2026-02-04T16:08:27.046Z",
    "dateReserved": "2026-01-13T15:37:45.966Z",
    "dateUpdated": "2026-02-04T16:08:27.046Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-GX3F-MW8M-6FF3

CVE-2026-23106 (GCVE-0-2026-23106)

Tags

Sightings

Nomenclature