Answer in brief
CVE-2026-64218 records a Unknown severity vulnerability in batman-adv: bla: fix report_work leak on backbone_gw purge. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64218 records a Unknown severity vulnerability in batman-adv: bla: fix report_work leak on backbone_gw purge. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=23721387c409087fd3b97e274f34d3ddc0970b74 <ce2c0ee4d76d5ee4b391fe0e31334361e25030ec || >=23721387c409087fd3b97e274f34d3ddc0970b74 <3423a45e5c3d3c5129f88143a9a969787d7d5a0a || >=23721387c409087fd3b97e274f34d3ddc0970b74 <f1303adb1e59582f76c22798a2e2e150e054a9e7 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <48663158222b3b7f6ee6791a67d512ede7fc94bb || >=23721387c409087fd3b97e274f34d3ddc0970b74 <eeddd7bab3d59c1e98642a204141f8c5d6194707 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <c6de1a5a9c406e30b91f1515a6ce05cc84023baa || >=23721387c409087fd3b97e274f34d3ddc0970b74 <95a7034661274cf5985708bd2f6d86ee46f88fa9 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <0459430add32ea41f3e2ef9351610e6d33627a6b | ce2c0ee4d76d5ee4b391fe0e31334361e25030ec, 3423a45e5c3d3c5129f88143a9a969787d7d5a0a, f1303adb1e59582f76c22798a2e2e150e054a9e7, 48663158222b3b7f6ee6791a67d512ede7fc94bb, eeddd7bab3d59c1e98642a204141f8c5d6194707, c6de1a5a9c406e30b91f1515a6ce05cc84023baa, 95a7034661274cf5985708bd2f6d86ee46f88fa9, 0459430add32ea41f3e2ef9351610e6d33627a6b |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=23721387c409087fd3b97e274f34d3ddc0970b74 <ce2c0ee4d76d5ee4b391fe0e31334361e25030ec || >=23721387c409087fd3b97e274f34d3ddc0970b74 <3423a45e5c3d3c5129f88143a9a969787d7d5a0a || >=23721387c409087fd3b97e274f34d3ddc0970b74 <f1303adb1e59582f76c22798a2e2e150e054a9e7 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <48663158222b3b7f6ee6791a67d512ede7fc94bb || >=23721387c409087fd3b97e274f34d3ddc0970b74 <eeddd7bab3d59c1e98642a204141f8c5d6194707 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <c6de1a5a9c406e30b91f1515a6ce05cc84023baa || >=23721387c409087fd3b97e274f34d3ddc0970b74 <95a7034661274cf5985708bd2f6d86ee46f88fa9 || >=23721387c409087fd3b97e274f34d3ddc0970b74 <0459430add32ea41f3e2ef9351610e6d33627a6b | ce2c0ee4d76d5ee4b391fe0e31334361e25030ec, 3423a45e5c3d3c5129f88143a9a969787d7d5a0a, f1303adb1e59582f76c22798a2e2e150e054a9e7, 48663158222b3b7f6ee6791a67d512ede7fc94bb, eeddd7bab3d59c1e98642a204141f8c5d6194707, c6de1a5a9c406e30b91f1515a6ce05cc84023baa, 95a7034661274cf5985708bd2f6d86ee46f88fa9, 0459430add32ea41f3e2ef9351610e6d33627a6b |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.