Menu

Star on GitHub · 3.2k

CVE-2026-64218

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entrie…

Published Jul 24, 2026EPSS 0.13%

Overview

CVE-2026-64218 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

batman-adv: bla: fix report_work leak on backbone_gw purge

batadv_bla_purge_backbone_gw() removes stale backbone gateway entries,

but fails to properly handle their associated report_work:

- If report_work is running, the purge must wait for it to finish before

freeing the backbone_gw, otherwise the worker may access freed memory

(e.g. bat_priv).

- If report_work is pending, the purge must cancel it and release the

reference held for that pending work item.

The previous implementation called hlist_for_each_entry_safe() inside a

spin_lock_bh() section, but cancel_work_sync() may sleep and therefore

cannot be called from within a spinlock-protected region.

Restructure the loop to handle one entry per spinlock critical section:

acquire the lock, find the next entry to purge, remove it from the hash

list, then release the lock before calling cancel_work_sync() and

dropping the hash_entry reference. Repeat until

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64218?

CVE-2026-64218 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64218?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64218?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64218?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64218 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all