CVE-2026-64095

batman-adv: bla: avoid double decrement of bla.num_requests

HIGH
7.1
CVSS Score
Published: July 19, 2026 at 03:40 PM UTC
Updated: August 11, 2026 at 04:28 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
HIGH7.1
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: avoid double decrement of bla.num_requests The bla.num_requests is increased when no request_sent was in progress. And it is decremented in various places (announcement was received, backbone is purged, periodic work). But the check if the request_sent is actually set to a specific state and the atomic_dec/_inc are not safe because they are not atomic (TOCTOU) and multiple such code portions can run concurrently. At the same time, it is necessary to modify request_sent (state) and bla.num_requests atomically. Otherwise batadv_bla_send_request() might set request_sent to 1 and is interrupted. batadv_handle_announce() can then set request_sent back to 0 and decrement num_requests before batadv_bla_send_request() incremented it. The two operations must therefore be locked. And since state (request_sent) and wait_periods are only accessed inside this lock, they can be converted to simpler datatypes. And to avoid that the bla.num_requests is touched by a parallel running context with a valid backbone_gw reference after batadv_bla_purge_backbone_gw() ran, a third state "stopped" is required to correctly signal that a backbone_gw is in the state of being cleaned up.

Affected

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

3.5 ≤ v < 5.10.2593.5 ≤ v < 5.15.2103.5 ≤ v < 6.1.1763.5 ≤ v < 6.12.933.5 ≤ v < 6.18.343.5 ≤ v < 6.6.1433.5 ≤ v < 7.0.113.5 ≤ v < 7.15.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.346.19 ≤ v < 7.0.116.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.9323721387c409087fd3b97e274f34d3ddc0970b747.1 rc17.1 rc27.1 rc37.1 rc4
Vendor states this is fixed in 1f013bc94154f2e78e97d0296175664224c796e0 (fixed)
Vendor states this is fixed in 45384612f29692fbf0c770200361a7acff90125c (fixed)
Vendor states this is fixed in 461f1e3dfb888701895b766446c55db2b10db705 (fixed)
Vendor states this is fixed in 5328b95960774f2e189f22485616bc7b8eb2f7e3 (fixed)
Vendor states this is fixed in 65497ad155a3246df177b5ef662cd6e5a32cb470 (fixed)
Vendor states this is fixed in 83ab69bd12b80f6ea169c8bea6977701b53a043d (fixed)
Vendor states this is fixed in 8ff9c59d1b7b48c2596878341a5310f32895d52b (fixed)
Vendor states this is fixed in a9393751ecf7e9096f93cb6eed02db4f79125765 (fixed)
Vendor states this is fixed in 3.5 (unaffected)
Vendor states this is fixed in 5.10.259 (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

7.1HIGHLinux
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