CVE-2026-99589

Description

A flaw was found in the Linux kernel's B.A.T.M.A.N. Advanced (batman-adv) mesh networking subsystem. When a local client roams back and transmits a frame before a translation table commit occurs, the driver fails to clear the roaming flag when re-adding the client entry. As a result, the node incorrectly reroutes unicast network traffic destined for the client to another mesh node, leading to packet loss and communication disruption.

Statement

This vulnerability is rated as having Moderate impact because exploitation requires an attacker to be on an adjacent network where B.A.T.M.A.N. Advanced mesh networking is actively deployed, and successful triggering depends on specific timing during client roaming events. Standard Red Hat Enterprise Linux installations do not configure or load mesh networking interfaces by default, substantially restricting exposure. Furthermore, the defect causes localized unicast traffic redirection and temporary packet delivery failure for the roaming client, rather than arbitrary code execution or host compromise.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.2N/AN/A
Attack VectorAdjacent NetworkN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

Red Hat: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L

Understanding the Weakness (CWE)

Access Control,Other

Technical Impact: Gain Privileges or Assume Identity; Varies by Context; Bypass Protection Mechanism

An attacker at the destination may be able to spoof trusted servers to steal data or cause a denial of service. The attacker can access any functionality that is inadvertently accessible to the source. - If the product allows an attacker to control/specify the destination, then the attacker can cause it to connect to an untrusted or malicious destination. For example, because UDP is a connectionless protocol, UDP packets can be spoofed by specifying a false source address in the packet; when the server receives the packet and sends a reply, it will specify a destination by using the source of the incoming packet - i.e., the false source. The server can then be tricked into sending traffic to the wrong host, which is effective for hiding the real source of an attack and for conducting a distributed denial of service (DDoS). As another example, server-side request forgery (SSRF) and XML External Entity (XXE) can be used to trick a server into making outgoing requests to hosts that cannot be directly accessed by the attacker due to firewall restrictions. If the product incorrectly specifies the destination, then an attacker who can control this destination might be able to spoof trusted components or servers.

Frequently Asked Questions

Want to get errata notifications? Sign up here.