CVE-2026-89948

batman-adv: bla: fix freeing of claims on meshif deletion

N/A
Published: September 16, 2026 at 10:32 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix freeing of claims on meshif deletion When the mesh interface is getting deleted, then batadv_bla_del_backbone_claims() (via batadv_bla_purge_backbone_gw()) could make sure that all claims gets removed. But this function is only executed when bat_priv->bla.claim_hash is not NULL. And since batadv_bla_free() is always setting it to NULL before it is (indirectly) called, it was never actually executed. But the batadv_bla_purge_claims() -> batadv_handle_unclaim() is at the moment too fragile because the BLA code is not handling the rehashing in batadv_bla_update_orig_address(). The stored backbone address doesn't have to be the one actually used for the hash bucket selection during the initial adding of the backbone. The batadv_handle_unclaim() can therefore fail to find the respective backbone for the unclaim and then stop the deletion. But the actual backbone_gw object is not needed for the unclaim because all relevant information is always provided by the caller. And the check for the existence of the backbone_gw doesn't provide any additional security check for the deletion of a claim.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

23721387c409087fd3b97e274f34d3ddc0970b743.5
Vendor states this is fixed in 76aedcde5a2489cc971d4d1e396e784a49565e96 (fixed)
Vendor states this is fixed in 844a95a734f178d56c7acce14c5cce2cecff7e1a (fixed)
Vendor states this is fixed in 871acdf97f64cee8398f72b88b89e8b4f4816dbe (fixed)
Vendor states this is fixed in 8d128c932bced74e3b1625ba3d7c78ef122a88a7 (fixed)
Vendor states this is fixed in 9a0c47023d3254048a1588534755d4476bcc3abc (fixed)
Vendor states this is fixed in aacffa780a37e06cd5a13d33740a6e96c3a67e6c (fixed)
Vendor states this is fixed in baeb1a28fd8e2f68193650d3664a8cd1adfd85c6 (fixed)
Vendor states this is fixed in f50edb69082a8ba990cc23d642089829f99afe6a (fixed)
Vendor states this is fixed in 3.5 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card