CVE-2026-99589
batman-adv: tt: clear ROAM flag when re-adding a pending local client
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: clear ROAM flag when re-adding a pending local client When a ROAMING_ADV is received for an announced local client, batadv_tt_local_mark_removed() sets BATADV_TT_CLIENT_ROAM, queues a DEL|ROAM change and marks the entry as BATADV_TT_CLIENT_PENDING. If the client sends a frame again before the next TTVN commit, batadv_tt_local_add_existing() only clears the PENDING flag and returns early. The ADD cancels the queued DEL, but the entry keeps the ROAM flag: * batadv_is_my_client() reports the client as not served by this node * batadv_tt_local_client_is_roaming() reroutes unicast frames for it to the node which sent the ROAMING_ADV The ROAM flag is only removed with the next frame of the client. Since BATADV_TT_CLIENT_ROAM is set together with BATADV_TT_CLIENT_PENDING, it has to be cleared also at the same time with BATADV_TT_CLIENT_PENDING when the client roamed back.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 068ee6e204e1f48ba24ec91ce40f5ca833a57a81; < fcf9688afc291bd9d383051c12e8bc148b4add62 (affected, git) ≥ 068ee6e204e1f48ba24ec91ce40f5ca833a57a81; < 658e7e37113f2ef875ea1b17e626f47d54c331ba (affected, git) ≥ 068ee6e204e1f48ba24ec91ce40f5ca833a57a81; < 32d45d029d9ffdeb99e86ed21406a70485fe08cc (affected, git) ≥ 068ee6e204e1f48ba24ec91ce40f5ca833a57a81; < cc2186d7854785b30d423f5d43757b086b300e55 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
3.8 (affected) ≥ 0; < 3.8 (unaffected, semver) ≥ 6.12.118; ≤ 6.12.* (unaffected, semver) ≥ 6.18.64; ≤ 6.18.* (unaffected, semver) ≥ 7.3.5; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.3 high |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H | CNA: Linux |
| 3.1 / 8.3 high |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/fcf9688afc291bd9d383051c12e8bc148b4add62CNA: Linux
- https://git.kernel.org/stable/c/658e7e37113f2ef875ea1b17e626f47d54c331baCNA: Linux
- https://git.kernel.org/stable/c/32d45d029d9ffdeb99e86ed21406a70485fe08ccCNA: Linux
- https://git.kernel.org/stable/c/cc2186d7854785b30d423f5d43757b086b300e55CNA: Linux
- https://git.kernel.org/stable/c/32d45d029d9ffdeb99e86ed21406a70485fe08cc416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/658e7e37113f2ef875ea1b17e626f47d54c331ba416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/cc2186d7854785b30d423f5d43757b086b300e55416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/fcf9688afc291bd9d383051c12e8bc148b4add62416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.