PT-2026-152638

CVE-2026-99759

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: don't drop local events queued during TVLV update
batadv tt tvlv container update() read the number of local changes without holding changes list lock. batadv tt local event() is not serialized by the commit lock and can queue new events before the changes list is flushed:
CPU0 CPU1 batadv tt tvlv container update() num = ...local changes; batadv tt local event() list add tail(...); ...local changes++; spin lock bh(&...changes list lock); /* 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 changes list must therefore be taken atomically. Events queued afterwards then stay in the tt.changes list 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 BATADV TT OGM APPEND MAX rounds before updating the container again. Until then, the outdated container with the previous TTVN would still be announced. The ogm append cnt 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 batadv tt local transition new() 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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾