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.
Affected products
linux: linux kernel
References8
- git.kernel.org/stable/c/0459430add32ea41f3e2ef9351610e6d33627a6b Patch
- git.kernel.org/stable/c/3423a45e5c3d3c5129f88143a9a969787d7d5a0a Patch
- git.kernel.org/stable/c/48663158222b3b7f6ee6791a67d512ede7fc94bb Patch
- git.kernel.org/stable/c/95a7034661274cf5985708bd2f6d86ee46f88fa9 Patch
- git.kernel.org/stable/c/c6de1a5a9c406e30b91f1515a6ce05cc84023baa Patch
- git.kernel.org/stable/c/ce2c0ee4d76d5ee4b391fe0e31334361e25030ec Patch
- git.kernel.org/stable/c/eeddd7bab3d59c1e98642a204141f8c5d6194707 Patch
- git.kernel.org/stable/c/f1303adb1e59582f76c22798a2e2e150e054a9e7 Patch
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 3 · as of 14 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.