CVE-2026-99588

Source
https://cve.org/CVERecord?id=CVE-2026-99588
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99588.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99588
Published
2026-11-20T05:49:17Z
Modified
2026-11-20T07:00:43Z
Summary
batman-adv: tt: only update flags for TT events
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99588.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee
Fixed
92fb8f25fee4c8820b54a18f694b74b3adb79f34
Fixed
4cec0f6207e551ec4081e84a37918060dd2b51a7
Fixed
326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe
Fixed
ad1fd828aa3944efc393b84b0d7c02483f1b5638

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99588.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.13.0
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99588.json"