CVE-2026-99760: batman-adv: tt: ignore ROAM flag of received ADD changes
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: ignore ROAM flag of received ADD changes
A received TT change (OGM diff or full table response) with the ROAM flag but without DEL is handled by batadvttglobaladd() like a ROAMINGADV:
a newly created global entry gets BATADVTTCLIENTROAM and is therefore excluded from the global CRC. The sender has it in its local CRC and the receiver has to request the full table again batadvttglobalpurgelocal() removes the local entry of the receiver. The receiver's own client is considered as roamed to the sender and frames for it are rerouted
The ROAM flag only has a meaning together with DEL. Drop it on reception to keep it from populating the global table with a temporary ROAMING entry which is not part of the CRC - and therefore causing a CRC mismatch.
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 - Compensating control
On reception, drop TT ADD changes that carry the ROAM flag without DEL.
Event History
Frequently Asked Questions
Which systems are affected in practice?
Systems using the Linux kernel's batman-adv mesh networking component are relevant. The issue concerns processing of received translation-table changes from mesh peers.
What is required to trigger the issue?
A received translation-table change, delivered through an OGM diff or full table response, must carry the ROAM flag without the DEL flag. The flawed handling treats it as a roaming advertisement.
What is the operational impact of the flawed handling?
It can create a temporary roaming entry that is excluded from the global CRC, causing a CRC mismatch and a request for the full table. It can also remove the receiver's local entry, causing its own client to be treated as roaming and traffic for that client to be rerouted.
What behavior does the fix implement?
The fix drops the ROAM flag when it is received without DEL. This prevents the entry from being added as a temporary roaming entry and avoids the resulting CRC mismatch and local-client rerouting behavior.