# CVE-2026-52913: batman-adv: v: stop OGMv2 on disabled interface

> A null pointer dereference in the Linux kernel's batman-adv module can cause a system crash when OGMv2 packets are sent on a disabled interface.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** BELL-CVE-2026-52913, DEBIAN-CVE-2026-52913, GHSA-7c77-5hjp-3754, ROOT-OS-DEBIAN-11-CVE-2026-52913, ROOT-OS-DEBIAN-12-CVE-2026-52913, ROOT-OS-UBUNTU-2204-CVE-2026-52913, ROOT-OS-UBUNTU-2404-CVE-2026-52913, UBUNTU-CVE-2026-52913

## What is CVE-2026-52913?

CVE-2026-52913 is a medium-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-52913?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-52913?

Apply the vendor's patch.

## Is CVE-2026-52913 being exploited?

There is no known exploitation of CVE-2026-52913 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52913 and fix it if it is affected.

What it is: CVE-2026-52913 is a medium-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52913 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52913/ (Markdown: https://insights.sbomify.com/CVE-2026-52913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52913
- OSV: https://osv.dev/vulnerability/CVE-2026-52913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52913/
Summaries are generated and may contain mistakes; the official description above is the record.