CVE-2025-68214 Details
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.
A race condition vulnerability has been identified in the Linux kernel's timer management functions, specifically within the timer_shutdown_sync() function. This vulnerability can lead to a NULL function pointer being accessed, causing a warning in the expire_timers() function. The issue arises when timer_shutdown_sync() clears the timer function while the timer is still active on another CPU, creating a scenario where a pending timer is left with a NULL function pointer. This vulnerability affects the Linux kernel stable tree.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for downloading the patched version are available on the Linux kernel official website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/176725f4848376530a0f0da9023f956afcc33585 | kernel.org | Patch |
| https://git.kernel.org/stable/c/1a975716cc8977f461e45e28e3e5977d46ad7a6a | kernel.org | Patch |
| https://git.kernel.org/stable/c/20739af07383e6eb1ec59dcd70b72ebfa9ac362c | kernel.org | Patch |
| https://git.kernel.org/stable/c/6665fbd7730b26d770c232b20d1b907e6a67a914 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a01efa7a780c42ac5170a949bd95c9786ffcc60a | kernel.org | Patch |
| https://git.kernel.org/stable/c/ba43ac025c4318241f8edf94f31d2eebab86991b | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.2, < 6.6.118 >= 6.7, < 6.12.60 >= 6.13, < 6.17.10 6.1.158 6.18 rc1 6.18 rc2 6.18 rc3 6.18 rc4 6.18 rc5 6.18 rc6 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 26, 2026 | Initial Analysis | [email protected] |
| Feb 12, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | New CVE Received | kernel.org |