CVE-2026-64093

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

HIGH
8.8
CVSS Score
Published: July 19, 2026 at 03:40 PM UTC
Updated: August 11, 2026 at 04:08 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.3%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.8 ≤ v < 5.15.2104.8 ≤ v < 6.1.1764.8 ≤ v < 6.12.934.8 ≤ v < 6.18.344.8 ≤ v < 6.6.1434.8 ≤ v < 7.0.114.8 ≤ v < 7.15.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.346.19 ≤ v < 7.0.116.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.9333a3bb4a3345bb511f9c69c913da95d4693e2a4e7.1 rc17.1 rc27.1 rc37.1 rc4
Vendor states this is fixed in 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c (fixed)
Vendor states this is fixed in 5bc2d50fb66b46f86543d5153a188eb1486d0b6e (fixed)
Vendor states this is fixed in 74a76634055462833446684fd526d73c290ea43a (fixed)
Vendor states this is fixed in 770bf0a35f0620b526fd4193889d1e77084e4c43 (fixed)
Vendor states this is fixed in 933880a8bc9b4042223a79255c0b1021cdc36991 (fixed)
Vendor states this is fixed in d5487249a81ea658717614009c8f46acc5b7101a (fixed)
Vendor states this is fixed in f86b20ec8d17d77bddc02c5c86cfa2389d84ecff (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.34 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.11 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card