Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-68214

medium

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…

Vendor / product: Linux — linux kernel

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 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 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.

CVSS
4.7
4.7 (CVSS v3.1)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-12-16 14:15
Modified: 2026-11-05 22:17
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-05 22:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥6.2 <6.6.118, ≥6.7 <6.12.60, ≥6.13 <6.17.10, 6.1.158, 6.18

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/176725f4848376530a0f0da9023f956afcc33585
Patch / mitigation: https://git.kernel.org/stable/c/1a975716cc8977f461e45e28e3e5977d46ad7a6a
Patch / mitigation: https://git.kernel.org/stable/c/20739af07383e6eb1ec59dcd70b72ebfa9ac362c
Patch / mitigation: https://git.kernel.org/stable/c/6665fbd7730b26d770c232b20d1b907e6a67a914
Patch / mitigation: https://git.kernel.org/stable/c/a01efa7a780c42ac5170a949bd95c9786ffcc60a
Patch / mitigation: https://git.kernel.org/stable/c/ba43ac025c4318241f8edf94f31d2eebab86991b

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 22:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs