batman-adv: bla: avoid CRC corruption due to parallel claim add
Summary
| CVE | CVE-2026-93203 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:16 UTC |
| Updated | 2026-09-17 17:18:16 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
batman-adv: bla: avoid CRC corruption due to parallel claim add
batadv_bla_add_claim() is used to add claims and modify the backbone of
claims for CLAIM frames from remote backbones and local packets. When it
handles a claim, it needs to either
* add the new claim's CRC to the backbone CRC
* remove the already existing claim's CRC from the old backbone and add it
to the new backbone
But when the "new" claim code was running in parallel to the "change
backbone" code, it can happen that the CRC was invalid because the
backbone_gw of the claim was changed twice in the "new" claim code path:
* CPU0 creates the claim for gateway A and publishes it in the claim
hash. The crc16 of the address has not yet been added to A's crc at
this point.
* CPU1 processes a claim frame of gateway B for the same client, finds
the just published claim, and performs the ownership change: it
switches the pointer to B, removes the crc16 from A's crc - which
never contained it - and adds it to B's crc.
* CPU0 continues behind the creation branch, unconditionally switches
the pointer back to A without compensating B's crc (its remove_crc
is false for the creation path), and finally adds the crc16 to A's
crc
The CRC is then wrong for both:
* claim belongs to A: but CRC is not part of backbone A's CRC
* claim doesn't belong to B: CRC is still part of backbone B's CRC
This wrong CRC is never recomputated from the stored claims. For local
backbone claims, this can also not recovered using syncs.
To avoid this, split the functionality in clear separate parts:
* new claim which always adds claim CRC to the backbone CRC (but never
changes the already set backbone_gw of the claim back)
* update of existing claim which automatically changes the backbone_gw
entry and only updates both backbone CRCs when there was an actual change |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 3d4a9ae2c69c0fe4c3c69587288241243bb7a39b git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 ad982d925f00d860d2467811256ffadcccd9e4a7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 d5b0e7574da5a485f4dbec32a15911900a4487c2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 a3e07db74f22a85aeeb51c600da5c98b9cbca11f git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 1d390db003cbb52cdd86837608bff3794501a5ea git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 8bcfa58c4277bff1882a23547c37ab08aa1de12f git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 e54602d9e38db8573f2097d60c7ea8be0a5af1fa git |
Not specified |
| CNA |
Linux |
Linux |
affected 23721387c409087fd3b97e274f34d3ddc0970b74 08645ab95768b88e2ff85a89211994651710465b git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.5 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.5 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.270 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.221 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/3d4a9ae2c69c0fe4c3c69587288241243bb7a39b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a3e07db74f22a85aeeb51c600da5c98b9cbca11f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8bcfa58c4277bff1882a23547c37ab08aa1de12f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ad982d925f00d860d2467811256ffadcccd9e4a7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/08645ab95768b88e2ff85a89211994651710465b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d5b0e7574da5a485f4dbec32a15911900a4487c2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1d390db003cbb52cdd86837608bff3794501a5ea |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e54602d9e38db8573f2097d60c7ea8be0a5af1fa |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.