Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

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.

Metrics

CVSS 3.x Severity and Vector Strings:

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

Weakness Enumeration

CWE-IDCWE NameSource
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')[email protected]

Affected Products

ProductVersions
linux linux kernel
>= 6.2, < 6.6.118
>= 6.7, < 6.12.60
>= 6.13, < 6.17.10
6.1.158
6.18 rc1

CPE

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.158:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:*

Remediation

  • No remediation found in references.

Change History

7 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2025-68214
NVD Published Date:
Dec 16, 2025
NVD Last Modified:
Nov 5, 2026
Source:
kernel.org
CVE-2025-68214 Details - Not Deferred