CVE-2026-64218
batman-adv: bla: fix report_work leak on backbone_gw purge
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 no more entries require purging.
INFO
Published Date :
July 24, 2026, 4:16 p.m.
Last Modified :
July 24, 2026, 4:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64218
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Acquire lock and find next entry to purge.
- Remove entry from hash list.
- Release lock before cancelling work.
- Free gateway and decrement reference.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64218.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64218 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64218
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64218 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64218 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': 'ce2c0ee4d76d5ee4b391fe0e31334361e25030ec', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': '3423a45e5c3d3c5129f88143a9a969787d7d5a0a', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': 'f1303adb1e59582f76c22798a2e2e150e054a9e7', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': '48663158222b3b7f6ee6791a67d512ede7fc94bb', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': 'eeddd7bab3d59c1e98642a204141f8c5d6194707', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': 'c6de1a5a9c406e30b91f1515a6ce05cc84023baa', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': '95a7034661274cf5985708bd2f6d86ee46f88fa9', 'versionType': 'git'}, {'status': 'affected', 'version': '23721387c409087fd3b97e274f34d3ddc0970b74', 'lessThan': '0459430add32ea41f3e2ef9351610e6d33627a6b', 'versionType': 'git'}], 'programFiles': ['net/batman-adv/bridge_loop_avoidance.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.5'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.5', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.258', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.209', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.175', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.142', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.92', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/batman-adv/bridge_loop_avoidance.c'], 'defaultStatus': 'affected'}] Added 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 no more entries require purging. Added Reference https://git.kernel.org/stable/c/0459430add32ea41f3e2ef9351610e6d33627a6b Added Reference https://git.kernel.org/stable/c/3423a45e5c3d3c5129f88143a9a969787d7d5a0a Added Reference https://git.kernel.org/stable/c/48663158222b3b7f6ee6791a67d512ede7fc94bb Added Reference https://git.kernel.org/stable/c/95a7034661274cf5985708bd2f6d86ee46f88fa9 Added Reference https://git.kernel.org/stable/c/c6de1a5a9c406e30b91f1515a6ce05cc84023baa Added Reference https://git.kernel.org/stable/c/ce2c0ee4d76d5ee4b391fe0e31334361e25030ec Added Reference https://git.kernel.org/stable/c/eeddd7bab3d59c1e98642a204141f8c5d6194707 Added Reference https://git.kernel.org/stable/c/f1303adb1e59582f76c22798a2e2e150e054a9e7