CVE-2026-99588

published 20 Nov 2026 · updated 20 Nov 2026

batman-adv: tt: only update flags for TT events

4.3MediumCVSS 4.3EPSS 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 ad1fd828aa3944efc393b84b0d7c02483f1b5638, Kernel 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe, Kernel 4cec0f6207e551ec4081e84a37918060dd2b51a7 and 4 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee <ad1fd828aa3944efc393b84b0d7c02483f1b5638, >=3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee <326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe, >=3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee <4cec0f6207e551ec4081e84a37918060dd2b51a7, >=3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee <92fb8f25fee4c8820b54a18f694b74b3adb79f34, =3.13ad1fd828aa3944efc393b84b0d7c02483f1b5638, 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe, 4cec0f6207e551ec4081e84a37918060dd2b51a7, 92fb8f25fee4c8820b54a18f694b74b3adb79f34
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=3.13.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-99588 severity on Zeptric[![CVE-2026-99588](https://zeptric.io/badge/cve/CVE-2026-99588.svg)](https://zeptric.io/cve/CVE-2026-99588)