CVE-2026-99588
Severity unknownNo known exploitationFix availablebatman-adv: tt: only update flags for TT events
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee before 4cec0f6207e551ec4081e84a37918060dd2b51a7 | 4cec0f6207e551ec4081e84a37918060dd2b51a7 | CVE Program |
| Linux | Linux | from 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee before 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe | 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe | CVE Program |
| Linux | Linux | from 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee before ad1fd828aa3944efc393b84b0d7c02483f1b5638 | ad1fd828aa3944efc393b84b0d7c02483f1b5638 | CVE Program |
| Linux | Linux | from 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee before 92fb8f25fee4c8820b54a18f694b74b3adb79f34 | 92fb8f25fee4c8820b54a18f694b74b3adb79f34 | CVE Program |
| Linux | Linux | 3.13 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 3.13 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe (opens in a new tab)
- https://git.kernel.org/stable/c/4cec0f6207e551ec4081e84a37918060dd2b51a7 (opens in a new tab)
- https://git.kernel.org/stable/c/92fb8f25fee4c8820b54a18f694b74b3adb79f34 (opens in a new tab)
- https://git.kernel.org/stable/c/ad1fd828aa3944efc393b84b0d7c02483f1b5638 (opens in a new tab)