CVE-2026-99589 in Linux
Summary
by MITRE • 11/20/2026
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: clear ROAM flag when re-adding a pending local client
When a ROAMING_ADV is received for an announced local client, batadv_tt_local_mark_removed() sets BATADV_TT_CLIENT_ROAM, queues a DEL|ROAM change and marks the entry as BATADV_TT_CLIENT_PENDING. If the client sends a frame again before the next TTVN commit, batadv_tt_local_add_existing() only clears the PENDING flag and returns early. The ADD cancels the queued DEL, but the entry keeps the ROAM flag:
* batadv_is_my_client() reports the client as not served by this node * batadv_tt_local_client_is_roaming() reroutes unicast frames for it to the node which sent the ROAMING_ADV
The ROAM flag is only removed with the next frame of the client.
Since BATADV_TT_CLIENT_ROAM is set together with BATADV_TT_CLIENT_PENDING, it has to be cleared also at the same time with BATADV_TT_CLIENT_PENDING when the client roamed back.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in the Linux kernel's batman-adv module involves a state management flaw within the translation table logic that handles local client tracking and roaming behavior. Specifically, the issue arises during the processing of ROAMING_ADV messages for announced local clients. When such an advertisement is received, the function batadv_tt_local_mark_removed() correctly sets the BATADV_TT_CLIENT_ROAM flag, queues a DEL|ROAM change, and marks the entry as BATADV_TT_CLIENT_PENDING to indicate that the client's presence needs verification or re-establishment. This sequence is designed to manage network topology changes where clients move between nodes in a mesh network. However, if the client subsequently sends a frame before the next Translation Table Version Number commit occurs, the function batadv_tt_local_add_existing() is invoked to handle this return.
The technical flaw lies in how batadv_tt_local_add_existing() processes the re-adding of this pending local client. While it correctly clears the BATADV_TT_CLIENT_PENDING flag and returns early after canceling the queued DEL operation, it fails to clear the previously set BATADV_TT_CLIENT_ROAM flag. This oversight results in a persistent state inconsistency where the entry retains the ROAM status even though the client has effectively returned or remained local. The ROAM flag is only cleared upon receiving the next frame from the client, creating a window of incorrect behavior during this interim period.
This state corruption leads to significant operational impacts on network performance and connectivity. Because BATADV_TT_CLIENT_ROAM remains set, two critical functions behave incorrectly for that specific client entry. First, batadv_is_my_client() reports the client as not served by the current node, which can lead to incorrect routing decisions or failure in local delivery of packets intended for this client. Second, and more critically, batadv_tt_local_client_is_roaming() determines that unicast frames destined for this client should be rerouted to the node that originally sent the ROAMING_ADV message. This causes unnecessary traffic redirection across the mesh network, increasing latency and consuming bandwidth on inter-node links without any actual benefit, as the client is effectively local again.
The root cause of this vulnerability can be classified under CWE-672, which refers to the use of operation after Expiration or Removal, specifically in the context of state flags not being properly reset when their associated conditions change. The logic assumes that clearing PENDING is sufficient for a full recovery of the client's local status, ignoring the coupled nature of the ROAM flag within this specific code path. This represents an incomplete cleanup procedure where dependent state variables are not synchronized during transitions back to a stable local state.
From a tactical perspective, this flaw aligns with ATT&CK techniques related to network evasion or disruption, as it can be exploited to cause denial-of-service conditions through increased latency and packet misrouting within the mesh infrastructure. An attacker aware of this behavior could potentially trigger repeated ROAMING_ADV messages followed by immediate client activity to keep clients in a suboptimal routing state, thereby degrading overall network performance for all users relying on that segment of the batman-adv mesh.
Mitigation strategies primarily involve applying the kernel patch that resolves this issue by ensuring that when BATADV_TT_CLIENT_PENDING is cleared during the re-addition process, the BATADV_TT_CLIENT_ROAM flag is also explicitly cleared at the same time. This ensures state consistency and prevents the incorrect rerouting of unicast traffic. Administrators should update their Linux kernels to versions containing this fix. Additionally, monitoring network performance metrics for unusual latency spikes or unexpected inter-node traffic patterns can help detect instances where this vulnerability might be actively impacting operations before a patch is applied.