CVE-2026-99759

published 20 Nov 2026 · updated 21 Nov 2026

batman-adv: tt: don't drop local events queued during TVLV update

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ed7a0dfdd370acb48be7a281df732c1bebcc7f1d, Kernel 5bfa79a27aee75e3f1d84f9b4d4358dbeb9b7505, Kernel 9c456c887ad9c8950097473590923ce8b553d488 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=a73105b8d4c765d9ebfb664d0a66802127d8e4c7 <ed7a0dfdd370acb48be7a281df732c1bebcc7f1d, >=a73105b8d4c765d9ebfb664d0a66802127d8e4c7 <5bfa79a27aee75e3f1d84f9b4d4358dbeb9b7505, >=a73105b8d4c765d9ebfb664d0a66802127d8e4c7 <9c456c887ad9c8950097473590923ce8b553d488, >=a73105b8d4c765d9ebfb664d0a66802127d8e4c7 <cd2ff491c8eed4773f4f50ae10c942e09db1f6c4, =3.1ed7a0dfdd370acb48be7a281df732c1bebcc7f1d, 5bfa79a27aee75e3f1d84f9b4d4358dbeb9b7505, 9c456c887ad9c8950097473590923ce8b553d488, cd2ff491c8eed4773f4f50ae10c942e09db1f6c4
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=3.1.0 <6.12.1186.18.64, 7.3.5, 6.12.118

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99759 severity on Zeptric[![CVE-2026-99759](https://zeptric.io/badge/cve/CVE-2026-99759.svg)](https://zeptric.io/cve/CVE-2026-99759)