Heimdall Security Logo

CVE-2025-68214

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 6.6.118, <=6.1.*, <=6.12.*, 6.17.10, <1a975716cc8977f461e45e28e3e5977d46ad7a6a, 0, <a01efa7a780c42ac5170a949bd95c9786ffcc60a, 6.18, <=6.6.*, 6.12.60, debbcf812d735003c96c5e5968a3cfa4e1fbd1af, 0cc04e80458a822300b93f82ed861a513edde194, <176725f4848376530a0f0da9023f956afcc33585, <6.2, 334c33aa487be406a149c8b87c38c8399d2dba8d, <ba43ac025c4318241f8edf94f31d2eebab86991b, 6.1.158, 6.1.159, <20739af07383e6eb1ec59dcd70b72ebfa9ac362c, <=*, <=6.17.*, <6665fbd7730b26d770c232b20d1b907e6a67a914, <6.1.159, 6.2

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.

Gravité et risque d'exploitation

CVE-2025-68214 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.6.118, <=6.1.*, <=6.12.*, 6.17.10, <1a975716cc8977f461e45e28e3e5977d46ad7a6a, 0, <a01efa7a780c42ac5170a949bd95c9786ffcc60a, 6.18, <=6.6.*, 6.12.60, debbcf812d735003c96c5e5968a3cfa4e1fbd1af, 0cc04e80458a822300b93f82ed861a513edde194, <176725f4848376530a0f0da9023f956afcc33585, <6.2, 334c33aa487be406a149c8b87c38c8399d2dba8d, <ba43ac025c4318241f8edf94f31d2eebab86991b, 6.1.158, 6.1.159, <20739af07383e6eb1ec59dcd70b72ebfa9ac362c, <=*, <=6.17.*, <6665fbd7730b26d770c232b20d1b907e6a67a914, <6.1.159, 6.2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE