High · published July 24, 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.
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 3.5, < 5.10.258 | 5.10.258 |
| linux/linux_kernel | ≥ 5.11, < 5.15.209 | 5.15.209 |
| linux/linux_kernel | ≥ 5.16, < 6.1.175 | 6.1.175 |
| linux/linux_kernel | ≥ 6.2, < 6.6.142 | 6.6.142 |
| linux/linux_kernel | ≥ 6.7, < 6.12.92 | 6.12.92 |
| linux/linux_kernel | ≥ 6.13, < 6.18.34 | 6.18.34 |
| linux/linux_kernel | ≥ 6.19, < 7.0.11 | 7.0.11 |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |