CVE-2026-64093

published 19 Jul 2026 · updated 28 Oct 2026

batman-adv: tp_meter: directly shut down timer on cleanup

8.8HighCVSS 8.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, Kernel 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, Kernel 5bc2d50fb66b46f86543d5153a188eb1486d0b6e and 10 more.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <5bc2d50fb66b46f86543d5153a188eb1486d0b6e, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <74a76634055462833446684fd526d73c290ea43a, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <770bf0a35f0620b526fd4193889d1e77084e4c43, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <933880a8bc9b4042223a79255c0b1021cdc36991, >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <d5487249a81ea658717614009c8f46acc5b7101a, =4.8f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 5bc2d50fb66b46f86543d5153a188eb1486d0b6e, 74a76634055462833446684fd526d73c290ea43a, 770bf0a35f0620b526fd4193889d1e77084e4c43, 933880a8bc9b4042223a79255c0b1021cdc36991, d5487249a81ea658717614009c8f46acc5b7101a
linux-kernel: Kernel>=5.16.0 <6.1.176, >=6.13.0 <6.18.34, >=6.19.0 <7.0.11, >=6.2.0 <6.6.143, >=6.7.0 <6.12.93, >=4.8.0 <5.15.2106.1.176, 6.18.34, 7.0.11, 6.6.143, 6.12.93, 5.15.210

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64093 severity on Zeptric[![CVE-2026-64093](https://zeptric.io/badge/cve/CVE-2026-64093.svg)](https://zeptric.io/cve/CVE-2026-64093)