CVE-2026-99588: batman-adv: tt: only update flags for TT events
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: only update flags for TT events
In the first implementation of the translation table events, it was only possible to announce:
ADD: new locally detected client DEL: disappeared local client
If an ADD event was queued and then a DEL event was queued in the same timeslot, it is valid to destroy both events because nothing actually changed for remode nodes
But with commit 3c4f7ab60cc2 ("batman-adv: improve the TT component to support runtime flag changes") and subsequent changes, it could also happen that there are extra ADD events:
ADD: NEW locally detected client ADD: already existing client with new flags DEL: disappeared local client
The first and the last type of event could in theory still be removed together from the (to be announced) events queue. But if the "update flags" ADD is dropped together with the DEL, it would still leave global translation table of a remote node in the incorrect state - believing that the client didn't disappear.
If a detected client was previously announced, a DEL event must only overwrite the "update flags" ADD but the DEL itself must still continue to exist in the (to be anounced) events queue. For now, adjustment of the announced flags is used for everything instead of dropping already queued up events completely.
Similarly, a DEL followed by an ADD caused both entries to be deleted. But the new ADD could announce flags changes which were not yet present for the client before it was marked for DELetion. The new ADD must therefore only overwrite the DEL - but still be kept.
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 event sequence can leave remote nodes with stale client information?
The problematic case is when an already announced client has an ADD event queued to update its flags and then a DEL event is queued after the client disappears. Dropping both events can cause a remote node's global translation table to continue believing that the client exists.
Which deployments are relevant to this issue?
This concerns Linux kernel deployments using batman-adv translation-table event propagation, particularly where runtime client flag updates can occur before a client deletion event.
Are fixed kernel versions identified?
No fixed version numbers are provided. The supplied stable-kernel references identify the relevant fixes by commit: 92fb8f25fee4c8820b54a18f694b74b3adb79f34, 4cec0f6207e551ec4081e84a37918060dd2b51a7, and 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe.