Skip to main content
VulnerabilityPublished Updated

CVE-2026-52914: Linux kernel · batman-adv: fix fragment reassembly length accounting

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in fdb2c96efb2baeb3725e9ce3ede8f1e36f5490f0 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fdb2c96efb2baeb3725e9ce3ede8f1e36f5490f0, f653b040dad1af70fa5cd4fe085e4758925480c9, e910dbf509125fe51ad68e4fa74dc8ab0a8e787a +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < fdb2c96efb2baeb3725e9ce3ede8f1e36f5490f0
Fixed in
  • fdb2c96efb2baeb3725e9ce3ede8f1e36f5490f0
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < f653b040dad1af70fa5cd4fe085e4758925480c9
Fixed in
  • f653b040dad1af70fa5cd4fe085e4758925480c9
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < e910dbf509125fe51ad68e4fa74dc8ab0a8e787a
Fixed in
  • e910dbf509125fe51ad68e4fa74dc8ab0a8e787a
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < e4f3f6b818aa6a678bc54a2d4e0bece2303c6a64
Fixed in
  • e4f3f6b818aa6a678bc54a2d4e0bece2303c6a64
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < 975563c5de1123dde1ec7946bf5556d20c89d74e
Fixed in
  • 975563c5de1123dde1ec7946bf5556d20c89d74e
LinuxLinuxAffected
  • ≥ 610bfc6bc99bc83680d190ebc69359a05fc7f605, < 37be61825b15534a16ff9cfc9546de155b6df982
Fixed in
  • 37be61825b15534a16ff9cfc9546de155b6df982

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix fragment reassembly length accounting batman-adv keeps a running payload length for queued fragments and uses it to validate a fragment chain before reassembly. That accounting currently allows the accumulated fragment length to be truncated during updates. As a result, malformed fragment chains can bypass the intended validation and drive reassembly with inconsistent length state, leading to a local denial of service. Fix the accounting by storing the accumulated length in a length-typed field and rejecting update overflows before the existing validation logic runs. The fix was verified against the original reproducer and against valid fragment reassembly paths.

References

Community reviews

Loading reviews…