CVE-2026-52913: Linux Kernel batman-adv NULL Pointer DoS Vulnerability
A vulnerability in the Linux kernel's batman-adv networking module can cause a system crash when network interfaces are disabled. The issue stems from code that continues sending mesh network announcements (OGMs) through interfaces that have been taken offline, leading to attempts to access memory that no longer contains valid data. An unprivileged local user with access to the affected system could trigger this crash, resulting in a denial of service.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-476
- Affected products
- 5 configuration(s)
- Published / Modified
- 2026-06-24 / 2026-07-08
NVD description (verbatim)
In the Linux kernel, the following vulnerability has been resolved: batman-adv: v: stop OGMv2 on disabled interface When a batadv_hard_iface is disabled, its mesh_iface pointer is set to NULL. However, batadv_v_ogm_send_meshif() may still dispatch OGMs via batadv_v_ogm_queue_on_if() for interfaces that have since lost their mesh_iface association. This results in a NULL pointer dereference when batadv_v_ogm_queue_on_if() unconditionally calls netdev_priv() on the now NULL hard_iface->mesh_iface to retrieve the batadv_priv. It is necessary to ensure that the batadv_v_ogm_queue_on_if() checks that it is using the same mesh_iface for which batadv_v_ogm_send_meshif() was called.
8 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-52913 is a NULL pointer dereference vulnerability in the batman-adv v15 implementation within the Linux kernel. When a batadv_hard_iface is disabled, its mesh_iface pointer is nullified; however, batadv_v_ogm_send_meshif() continues to dispatch Optimized Link State Routing v2 (OGMv2) packets through batadv_v_ogm_queue_on_if(). This function unconditionally dereferences the now-NULL mesh_iface pointer via netdev_priv() to retrieve the batadv_priv structure, triggering a kernel panic. The root cause is insufficient validation that the mesh_iface used during OGM transmission matches the interface context at dispatch time. The fix requires batadv_v_ogm_queue_on_if() to verify mesh_iface consistency before proceeding.
Business impact
Organizations running batman-adv for mesh networking (common in community networks, edge computing deployments, and some embedded systems) face availability disruption. A local attacker can remotely trigger kernel panics, forcing system restarts and interrupting services. For mission-critical infrastructure relying on batman-adv for redundancy or network automation, this becomes a significant operational risk. Recovery requires manual intervention or orchestrated restarts, adding operational overhead.
Affected systems
The Linux kernel across multiple versions that include the batman-adv module. Exposure depends on whether batman-adv is compiled into the kernel or available as a module, and whether mesh networking is actively configured. Systems using batman-adv for wireless mesh networks, edge gateways, or network-attached appliances are directly affected. Default Linux distributions may include batman-adv but typically do not enable it unless explicitly configured by administrators.
Exploitability
Exploitability is straightforward for local attackers (CVSS vector AV:L). No special privileges are required beyond standard user-level access (PR:L), and no user interaction is necessary. An attacker can reliably trigger the crash by causing network interface state transitions on a system with batman-adv enabled and mesh networking active. The vulnerability does not enable privilege escalation or data theft, but denial of service is trivial to achieve.
Remediation
Apply the Linux kernel patch that adds a mesh_iface consistency check within batadv_v_ogm_queue_on_if(). This ensures OGM packets are only queued on interfaces that remain associated with their original mesh context. Verify the patch version against the kernel security advisory, as fixes may be backported across multiple kernel branches. Alternatively, disable batman-adv if mesh networking is not required, or restrict local user access on systems where batman-adv is active.
Patch guidance
Monitor linux.org security advisories for kernel releases incorporating the batman-adv v15 fix. The vulnerability affects the batman-adv subsystem specifically; patch availability will depend on your kernel branch and distribution. Check your vendor's security bulletins—Red Hat, Debian, Ubuntu, and other major distributions will publish guidance once patches are available. Apply patches during your standard kernel update cycle; this does not require emergency action unless batman-adv mesh networking is critical to your operations.
Detection guidance
Monitor system logs for kernel NULL pointer dereference panics mentioning batman-adv, batadv_v_ogm_send_meshif, or batadv_v_ogm_queue_on_if in the call stack. Kernel crash dumps (vmcore files) will show the dereferenced NULL pointer in netdev_priv() calls. On systems with batman-adv enabled, correlate crashes with interface state changes (ifdown, ifup, or dynamic interface removal). Intrusion detection signatures should flag repeated kernel panic patterns on systems where batman-adv mesh is active.
Why prioritize this
Although the CVSS score of 5.5 indicates medium severity, prioritization should account for operational context. Systems without batman-adv mesh networking enabled face no exposure and require no action. For organizations actively deploying batman-adv (wireless mesh providers, edge computing platforms, community networks), this becomes a high-priority availability risk despite the low CVSS score. Triage by assessing batman-adv deployment scope within your infrastructure.
Risk score, explained
The CVSS 5.5 MEDIUM rating reflects local-only attack surface (AV:L), low privilege requirements (PR:L), and impact limited to availability (A:H with C:N, I:N). No network-based attack path exists, no privilege escalation occurs, and no confidentiality or integrity loss is possible. The score appropriately reflects the denial-of-service nature of the vulnerability without overstating risk for systems where batman-adv is not deployed.
Frequently asked questions
Do I need to patch if batman-adv is not configured on my systems?
No. This vulnerability only affects systems where the batman-adv module is compiled into the kernel and actively used for mesh networking. If batman-adv is not enabled or in use, the vulnerable code path is not reachable. Check your kernel configuration (grep BATMAN /boot/config-*) and verify batman-adv is not running (ip link show | grep batman).
Can this vulnerability be exploited remotely over the network?
No. The attack vector is local-only (AV:L per CVSS), meaning an attacker must have direct access to the affected system with unprivileged user-level permissions. Network-based attacks are not possible, even against systems running batman-adv mesh networks.
What is batman-adv and why would we be using it?
Batman-adv (Better Approach to Mobile Ad-hoc Networking—Advanced) is a Linux kernel module that implements mesh networking, allowing devices to forward traffic through multiple hops without centralized infrastructure. It's used in wireless mesh deployments, community networks, IoT edge gateways, and some embedded systems. Most traditional enterprise networks do not use batman-adv; it's common in specialized edge and mesh scenarios.
If we experience a kernel panic, how do we confirm it's related to this vulnerability?
Check the kernel panic message and vmcore dump for references to batadv_v_ogm_send_meshif, batadv_v_ogm_queue_on_if, or netdev_priv in the call stack. Correlate the timing with batman-adv interface state changes. If you have access to kernel logs, search for NULL pointer dereference in the batman-adv subsystem. If batman-adv is not enabled, the panic is unrelated to CVE-2026-52913.
This analysis is based on the vulnerability description and publicly available CVE data as of the published date. CVSS scores and severity ratings are provided by the National Vulnerability Database and reflect general risk assessment; actual impact varies with deployment context. Patch availability, version numbers, and distribution-specific guidance should be verified against official vendor security advisories before implementation. This assessment does not constitute professional security advice; organizations should conduct their own risk assessments and consult vendor documentation. No exploit code or weaponized proof-of-concept techniques are provided herein. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-71313MEDIUMLinux Kernel PCI Endpoint NULL Pointer Dereference
- CVE-2026-46118MEDIUMLinux Kernel PAPR Hypervisor Pipe Null Pointer Dereference (POWER Systems)
- CVE-2026-46127MEDIUMLinux Kernel OCRDMA Null Pointer Dereference (DoS)
- CVE-2026-46134MEDIUMLinux Kernel cros_ec Mutex Initialization DoS Vulnerability
- CVE-2026-46188MEDIUMLinux Octeon EP VF NULL Pointer Dereference Denial of Service
- CVE-2026-46211MEDIUMLinux Kernel MSM DRM NULL Pointer and Silent Error in gem_info_get_metadata
- CVE-2026-46216MEDIUMLinux Intel Arc GPU NULL Pointer Dereference (HDCP)
- CVE-2026-46222MEDIUMLinux Rockchip RKCam Driver Null Pointer Dereference