CVE-2026-64092

batman-adv: tp_meter: fix tp_vars reference leak in receiver shutdown

MEDIUM
5.5
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
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: fix tp_vars reference leak in receiver shutdown The receiver shutdown timer handler, batadv_tp_receiver_shutdown(), is responsible for releasing the tp_vars reference it holds. However, the existing logic for coordinating this release with batadv_tp_stop_all() was flawed. timer_shutdown_sync() guarantees the timer will not fire again after it returns, but it returns non-zero only when the timer was pending at the time of the call. If the timer had already expired (and batadv_tp_stop_all() would unsucessfully try to rearm itself), batadv_tp_stop_all() skips its batadv_tp_vars_put(), and batadv_tp_receiver_shutdown() fails to put its own reference as well. Fix this by introducing a new atomic variable receiving that is set to 1 when the receiver is initialized and cleared atomically with atomic_xchg() by whichever side claims it first. Only the side that observes the transition from 1 to 0 is responsible for releasing the tp_vars timer reference, eliminating the uncertainty.

Affected

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

v ≥ 5.10.2595.10.259 ≤ v < 5.116.12.90 ≤ v < 6.12.926.18.32 ≤ v < 6.18.346.6.140 ≤ v < 6.6.1427.0.9 ≤ v < 7.0.11268078acae72daa12b17b2b299701cb9924e469a26dfeee8db81354bfdade155f27f9e16510ad1963660dab86f93319178a24667f6998526dc4355d3d3cf6a7314aca4df0a6dde28ce784a2a30d01665.10.25958943b7ea356294749dae3e75b96c0ee292c00be5e7d0ac936354c36810e74ac3056b334ed1f40586.12.906.18.326.6.1407.0.97.1 rc479bc0eaeef2c5797317bf2da8e3159a74d62ec478634c1dbd73adb74d40533ebb7e914efb82e71fb
Vendor states this is fixed in 0b1bedf114ea93fef929b31f0d70a9eedcc601de (fixed)
Vendor states this is fixed in 297e1bc4a915b7cd3e65a79ed906b23fb3d7aaae (fixed)
Vendor states this is fixed in 77098e4bea37af51d3962efa88a5af2ea5e1ac57 (fixed)
Vendor states this is fixed in 7715c73f33260af724d734c41b794457e9be8dbc (fixed)
Vendor states this is fixed in a9f0bfd624ee8a286d6fd2bf0f796e730efb49b0 (fixed)
Vendor states this is fixed in b285bc0a97f43823a4967fb6d286de4c7f53d541 (fixed)
Vendor states this is fixed in d078501dde9b57210f1808cdef4b59463d1f5fc8 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.12.92, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.18.34, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.142, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.11, so it looks safe — our inference, not a vendor statement

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-Other

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