Skip to main content
VulnerabilityPublished

CVE-2026-99588: Linux kernel · batman-adv: tt: only update flags for TT events

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ad1fd828aa3944efc393b84b0d7c02483f1b5638 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ad1fd828aa3944efc393b84b0d7c02483f1b5638, 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe, 92fb8f25fee4c8820b54a18f694b74b3adb79f34 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to ad1fd828aa3944efc393b84b0d7c02483f1b5638, 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe, 92fb8f25fee4c8820b54a18f694b74b3adb79f34 or 4cec0f6207e551ec4081e84a37918060dd2b51a7.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee, < ad1fd828aa3944efc393b84b0d7c02483f1b5638
Fixed in
  • ad1fd828aa3944efc393b84b0d7c02483f1b5638
LinuxLinuxAffected
  • ≥ 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee, < 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe
Fixed in
  • 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe
LinuxLinuxAffected
  • ≥ 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee, < 92fb8f25fee4c8820b54a18f694b74b3adb79f34
Fixed in
  • 92fb8f25fee4c8820b54a18f694b74b3adb79f34
LinuxLinuxAffected
  • ≥ 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee, < 4cec0f6207e551ec4081e84a37918060dd2b51a7
Fixed in
  • 4cec0f6207e551ec4081e84a37918060dd2b51a7
LinuxLinuxAffected
  • =3.13
Fixed in–

Description

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.

References

Community reviews

Loading reviews…