CVE-2026-52922: Linux batman-adv NULL Pointer Dereference DoS
A bug in the Linux kernel's batman-adv networking module can crash systems when memory allocation fails during DHT (Distributed Hash Table) forwarding operations. When the kernel tries to duplicate network packets for wireless mesh routing, it doesn't check if the duplication succeeded before trying to use the packet. If memory is scarce and duplication fails, the code attempts to process a NULL pointer, causing a kernel panic. This affects systems using batman-adv, typically mesh networks and certain wireless setups.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/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: dat: handle forward allocation error batadv_dat_forward_data() calls pskb_copy_for_clone() to duplicate an skb for each DHT candidate, but does not check the return value before passing it to batadv_send_skb_prepare_unicast_4addr(). That function dereferences the skb unconditionally, so a failed allocation triggers a NULL pointer dereference. Skip forwarding to the current DHT candidate on allocation failure.
8 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-52922 is a NULL pointer dereference in batman-adv's DAT (Distributed ARP Table) module. The batadv_dat_forward_data() function calls pskb_copy_for_clone() to create packet copies for each DHT candidate without validating the return value. Subsequent dereferencing of the potentially NULL skb in batadv_send_skb_prepare_unicast_4addr() leads to a kernel panic. The vulnerability stems from missing error handling for memory allocation failure in a packet forwarding path. The fix involves checking allocation success and skipping the affected DHT candidate if duplication fails, rather than proceeding with a NULL pointer.
Business impact
Systems relying on batman-adv for mesh networking or wireless connectivity face denial-of-service risk. An attacker able to trigger memory pressure or stress the DHT forwarding path could force kernel crashes, disrupting network availability. This is particularly relevant for edge deployments, IoT mesh networks, and community wireless infrastructure that depend on batman-adv. Organizations running affected kernels in memory-constrained environments or under high packet load face elevated risk of unplanned downtime.
Affected systems
The Linux kernel with batman-adv module compiled and enabled is affected. This includes various Linux distributions and embedded systems using batman-adv for mesh networking. The vulnerability impacts kernel versions before the fix was merged; specific patched versions should be verified against your distribution's kernel advisories. Systems not using batman-adv, or those with the module disabled, are not affected.
Exploitability
This is a local denial-of-service vulnerability rather than a remote code execution path. Exploitability requires either triggering genuine memory pressure or crafting a high volume of DHT forwarding requests to stress allocation paths. The attack surface is present on any system with batman-adv enabled and reachable network interfaces. No authentication or user interaction is required; an attacker on the mesh network can trigger the condition. Active exploitation in the wild is not reported (KEV status: not currently in CISA's Known Exploited Vulnerabilities catalog).
Remediation
Apply kernel updates that include the batman-adv DAT allocation error fix. For most distributions, this is available through standard kernel security updates. Verify the patch commit resolves the NULL pointer dereference in batadv_dat_forward_data(). Alternatively, disable batman-adv if not essential to your infrastructure. Test patched kernels in staging environments before production rollout, particularly for memory-constrained systems where allocation failures may be more likely.
Patch guidance
Consult your Linux distribution's security advisories for kernel updates addressing CVE-2026-52922. Patch availability depends on your kernel branch and distribution (e.g., RHEL, Ubuntu, Debian, Alpine). Kernel version numbers differ across distributions, so verify against your vendor's advisory rather than assuming a specific upstream version. Most distributions have released patches through their standard update channels. Reboot is required after kernel updates. For long-term support kernels, patches may be backported separately; check your distribution's release notes.
Detection guidance
Monitor kernel logs (dmesg, syslog) for NULL pointer dereference crashes mentioning batman-adv or batadv_dat functions. Look for kernel panic messages with stack traces referencing batadv_send_skb_prepare_unicast_4addr(). In environments using batman-adv, observe packet loss or sudden mesh network disconnections coinciding with memory pressure events. Use kernel crash dump analysis tools to correlate crashes with allocation failures. Network monitoring tools can detect unusual mesh traffic patterns that might stress the DHT forwarding path, though the vulnerability itself is triggered by allocation pressure rather than specific packet sequences.
Why prioritize this
High CVSS score (7.5) reflects the availability impact, but limited by lack of remote code execution or data breach risk. The vulnerability is straightforward to remediate via kernel update. Prioritize patching for systems where batman-adv is actively used and where network availability is critical. Memory-constrained systems, edge deployments, and high-traffic mesh networks should be prioritized. Systems without batman-adv enabled can defer patching to routine maintenance windows.
Risk score, explained
CVSS 3.1 score of 7.5 (HIGH) reflects a network-accessible denial-of-service vulnerability with no authentication barrier and high impact to availability. The score does not account for confidentiality or integrity (both unaffected), and assumes local network reach to the mesh (AV:N reflects network-adjacent attack surface on mesh topologies). The lack of widespread active exploitation and the simplicity of the fix prevent a CRITICAL rating, but the high availability impact and ease of triggering under memory pressure justify HIGH severity.
Frequently asked questions
Can this vulnerability be exploited remotely without being on the mesh network?
No. The attack requires either network access to the mesh where batman-adv is deployed, or the ability to trigger memory pressure on the affected system. External remote exploitation is not feasible. However, any attacker on the mesh network can trigger the condition.
Do I need to patch if I don't use batman-adv?
No. This vulnerability only affects systems with batman-adv compiled into the kernel and explicitly enabled. If batman-adv is not part of your kernel configuration or is disabled, you are not at risk and patching for this specific CVE is not necessary.
What happens when the vulnerability is triggered?
The kernel experiences a NULL pointer dereference, which causes a kernel panic and system crash. There is no silent failure or graceful degradation; the affected mesh network node will reboot or hang. This is a denial-of-service condition, not data loss or theft.
Should I disable batman-adv instead of patching?
Disabling batman-adv is a valid mitigation if the module is not essential. However, for systems actively relying on mesh networking, patching is the recommended approach as it preserves functionality while eliminating the vulnerability.
This analysis is based on the CVE description and CVSS vector provided. Specific patch version numbers, distribution timelines, and affected kernel versions should be verified against your Linux vendor's official security advisory. This vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog. The information provided is for security awareness and patch planning; it does not constitute professional security advice for your specific environment. Test all kernel updates in non-production systems before deployment. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-46110HIGHLinux stmmac NULL Dereference DoS Vulnerability
- CVE-2026-46114HIGHLinux Kernel RDMA RXE Remote Memory Leak via Malformed ATOMIC_WRITE
- CVE-2026-52929HIGHLinux SCTP Null-Pointer Dereference in Stream Rollback
- CVE-2026-52951HIGHLinux Xe DRM DMA-buf Race Condition – Local DoS via GPU Memory Import
- CVE-2026-52957HIGHLinux Kernel Ceph Null Pointer Dereference Denial of Service
- CVE-2026-8035HIGHNI-PAL Kernel Driver NULL Pointer Dereference DoS Vulnerability
- CVE-2025-71313MEDIUMLinux Kernel PCI Endpoint NULL Pointer Dereference
- CVE-2026-46118MEDIUMLinux Kernel PAPR Hypervisor Pipe Null Pointer Dereference (POWER Systems)