CVE-2026-64092

published 19 Jul 2026 · updated 17 Nov 2026

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

5.0MediumEPSS 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 d078501dde9b57210f1808cdef4b59463d1f5fc8, Kernel 6.12.92, Kernel 6.18.34 and 9 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=8634c1dbd73adb74d40533ebb7e914efb82e71fb <d078501dde9b57210f1808cdef4b59463d1f5fc8, >=6.12.90 <6.12.92, >=6.18.32 <6.18.34, >=6.6.140 <6.6.142, >=7.0.9 <7.0.11, >=79bc0eaeef2c5797317bf2da8e3159a74d62ec47 <0b1bedf114ea93fef929b31f0d70a9eedcc601de, =5e7d0ac936354c36810e74ac3056b334ed1f4058, >=03660dab86f93319178a24667f6998526dc4355d <b285bc0a97f43823a4967fb6d286de4c7f53d541, >=268078acae72daa12b17b2b299701cb9924e469a <7715c73f33260af724d734c41b794457e9be8dbc, >=26dfeee8db81354bfdade155f27f9e16510ad196 <a9f0bfd624ee8a286d6fd2bf0f796e730efb49b0, >=3d3cf6a7314aca4df0a6dde28ce784a2a30d0166 <77098e4bea37af51d3962efa88a5af2ea5e1ac57, >=5.10.259 <5.11, >=58943b7ea356294749dae3e75b96c0ee292c00be <297e1bc4a915b7cd3e65a79ed906b23fb3d7aaaed078501dde9b57210f1808cdef4b59463d1f5fc8, 6.12.92, 6.18.34, 6.6.142, 7.0.11, 0b1bedf114ea93fef929b31f0d70a9eedcc601de, b285bc0a97f43823a4967fb6d286de4c7f53d541, 7715c73f33260af724d734c41b794457e9be8dbc, a9f0bfd624ee8a286d6fd2bf0f796e730efb49b0, 77098e4bea37af51d3962efa88a5af2ea5e1ac57, 5.11, 297e1bc4a915b7cd3e65a79ed906b23fb3d7aaae
linux-kernel: Kernel>=6.12.90 <6.12.92, >=6.18.32 <6.18.34, >=6.6.140 <6.6.142, >=7.0.9 <7.0.11, >=5.10.259 <5.116.12.92, 6.18.34, 6.6.142, 7.0.11, 5.11

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-64092 severity on Zeptric[![CVE-2026-64092](https://zeptric.io/badge/cve/CVE-2026-64092.svg)](https://zeptric.io/cve/CVE-2026-64092)