The batman-adv driver contains a synchronization flaw where batadv_v_elp_get_throughput() can be invoked while the RTNL lock is already held. When the associated work queue item is cancelled via cancel_delayed_work_sync() in batadv_v_elp_iface_disable(), the attempt to acquire the RTNL lock again can block, resulting in a deadlock. This lock contention can stall critical kernel networking paths and cause the network stack to become unresponsive, effectively denying network services. The weakness is a classic instance of improper locking leading to a deadlock (CWE‑367).

All Linux kernel releases that ship the batman-adv driver before the patch, regardless of distribution vendor, are affected. The vendor is Linux, product is the Linux kernel, and no specific version range is supplied, so any active batman‑adv implementation that predates the fix is vulnerable.

Explicit exploitation metrics are not available: the EPSS score is not published and the cylinder is not listed in the CISA KEV catalog. The vulnerability is a local kernel race that can cause a deadlock; therefore the most likely attack vector requires local code execution or the presence of a malicious module that can trigger the problematic path. Because the impact is a denial of service and the severity rating is undefined, the risk can be considered moderate to high in environments where batman-adv is critical for network connectivity.