CVE-2026-64093

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <5bc2d50fb66b46f86543d5153a188eb1486d0b6e, <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, <00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 0, <74a76634055462833446684fd526d73c290ea43a, 6.1.176, 5.15.210, <f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, <=6.6.*, <770bf0a35f0620b526fd4193889d1e77084e4c43, <933880a8bc9b4042223a79255c0b1021cdc36991, 6.18.34, 7.1, <=6.18.*, 7.0.11, 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, 4.8, <=*, <=5.15.*, <d5487249a81ea658717614009c8f46acc5b7101a, <4.8, 6.6.143

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup batadv_tp_sender_cleanup() was calling timer_delete_sync() followed by timer_delete() to guard against the timer handler re-arming itself between the two calls. This double-deletion hack relied on the sending status being set to 0 to suppress re-arming. Replace both calls with a single timer_shutdown_sync(). This function both waits for any running timer callback to complete (like timer_delete_sync()) and permanently disarms the timer so it cannot be re-armed afterwards, making re-arming prevention unconditional and self-documenting. The re-arming property is also required because otherwise: 1. context 0 (batadv_tp_recv_ack()) checks in batadv_tp_reset_sender_timer() if sending is still 1 -> it is 2. context 1 changes in batadv_tp_sender_shutdown() sending to 0 and in this process forces the kthread to stop timer in batadv_tp_sender_cleanup() 3. context 0 continues in batadv_tp_reset_sender_timer() and rearms the timer -> but the reference for it is already gone

Gravité et risque d'exploitation

CVE-2026-64093 obtient un score CVSS de 8.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.35 %, ce qui la place devant 26.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <5bc2d50fb66b46f86543d5153a188eb1486d0b6e, <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, <00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 0, <74a76634055462833446684fd526d73c290ea43a, 6.1.176, 5.15.210, <f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, <=6.6.*, <770bf0a35f0620b526fd4193889d1e77084e4c43, <933880a8bc9b4042223a79255c0b1021cdc36991, 6.18.34, 7.1, <=6.18.*, 7.0.11, 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, 4.8, <=*, <=5.15.*, <d5487249a81ea658717614009c8f46acc5b7101a, <4.8, 6.6.143) 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