CVE-2026-99759: batman-adv: tt: don't drop local events queued during TVLV update
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: don't drop local events queued during TVLV update
batadvtttvlvcontainerupdate() read the number of local changes without holding changeslistlock. batadvttlocalevent() is not serialized by the commitlock and can queue new events before the changeslist is flushed:
CPU0 CPU1 batadvtttvlvcontainerupdate() num = ...localchanges; batadvttlocalevent() listaddtail(...); ...localchanges++; spinlockbh(&...changeslistlock); / only num events copied but all freed /
The additional events were freed without ever being sent. Other nodes will only notice this via a CRC mismatch and must request the full table.
The number of changes and the changeslist must therefore be taken atomically. Events queued afterwards then stay in the tt.changeslist for the next TT round.
The changes can no longer be kept for the next round when the TVLV buffer allocation fails. But they would be sent with a skipped TTVN anyway, so the other nodes have to request the full table in this case either way. The last changeset is only dropped in this case when the TTVN was incremented. Without new changes, it still describes the current TTVN.
Previously, the unconsumed changes caused a retry of the TVLV container update in the next commit round. Since the changes are now consumed, the next round would only take the path without changes and wait for BATADVTTOGMAPPENDMAX rounds before updating the container again. Until then, the outdated container with the previous TTVN would still be announced. The ogmappendcnt is therefore reset on failure to retry the update in the next OGM interval.
This doesn't make the CRC consistent with the announced changeset. The local table modifications are still not serialized with the commit and batadvttlocaltransitionnew() can still make a client part of the CRC for which the event is only part of the next TT round. Such an inconsistency is detected by the CRC check of the other nodes and solved via a full table request.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What deployments are exposed to this issue?
The issue affects Linux kernel deployments using batman-adv translation-table updates. It requires concurrent local translation-table events while batadv_tt_tvlv_container_update() is reading and flushing the queued change list.
What is the operational impact if the race occurs?
Newly queued local events can be freed without being sent to other mesh nodes. Peers detect the inconsistency through a CRC mismatch and must request the full translation table, causing synchronization to fall back from incremental updates to a full-table request.
How can an administrator tell that this behavior has occurred?
Other nodes noticing a translation-table CRC mismatch and requesting the full table is the described indication. The provided information does not identify a specific log message or diagnostic command.