Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-68214timers: Fix NULL function pointer race in timer_shutdown_sync()

Description

In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers(). Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-68214, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected debbcf812d735003c96c5e5968a3cfa4e1fbd1af – < ba43ac025c4318241f8edf94f31d2eebab86991b
    • affected 334c33aa487be406a149c8b87c38c8399d2dba8d – < 1a975716cc8977f461e45e28e3e5977d46ad7a6a
    • affected 0cc04e80458a822300b93f82ed861a513edde194 – < 6665fbd7730b26d770c232b20d1b907e6a67a914
    • affected 0cc04e80458a822300b93f82ed861a513edde194 – < 176725f4848376530a0f0da9023f956afcc33585
    • affected 0cc04e80458a822300b93f82ed861a513edde194 – < a01efa7a780c42ac5170a949bd95c9786ffcc60a
    • affected 0cc04e80458a822300b93f82ed861a513edde194 – < 20739af07383e6eb1ec59dcd70b72ebfa9ac362c
    • affected 6.1.158 – < 6.1.159
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.118 – ≤ 6.6.*
    • unaffected 6.12.60 – ≤ 6.12.*
    • unaffected 6.17.10 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68214 badge
[![CVE-2025-68214](https://cveledger.app/badge/CVE-2025-68214.svg)](https://cveledger.app/cve/CVE-2025-68214)

Record last updated .