CVE-2026-52931: Linux kernel · batman-adv: tp_meter: avoid use of uninit sender vars
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in ecdaa3e4d91040206afe21bc8a0d1198a0971ff3 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% 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 ecdaa3e4d91040206afe21bc8a0d1198a0971ff3, dc2ae5fbd2dadc26735092f140b246841d969a11, 85397e48afe6be83ffca5ad3f4792296bfc81d3d +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: avoid use of uninit sender vars batadv_tp_recv_ack() and batadv_tp_stop() are only valid for tp_vars in the BATADV_TP_SENDER role. When called with a BATADV_TP_RECEIVER role, it proceeds to read sender-only members that were never initialized, leading to undefined behavior. This can be triggered when a node that is currently acting as a receiver in an ongoing tp_meter session receives a malicious ACK packet. Guard against this by checking tp_vars->role immediately after the lookup and bailing out if it is not BATADV_TP_SENDER, before any of those members are accessed.
References
- git.kernel.org/stable/c/0e388af04b3958b178a1b979527f93eb46ea1fee (opens in a new tab)
- git.kernel.org/stable/c/1a21c055f66e78973712a4a1be2a554f1ee2e4f4 (opens in a new tab)
- git.kernel.org/stable/c/9884c9c02d3c90e9215db3c5128f59045d20ae91 (opens in a new tab)
- git.kernel.org/stable/c/53f931e0146ae5bdab4cba302646827d06b3794b (opens in a new tab)
- git.kernel.org/stable/c/ecdaa3e4d91040206afe21bc8a0d1198a0971ff3 (opens in a new tab)
- git.kernel.org/stable/c/dc2ae5fbd2dadc26735092f140b246841d969a11 (opens in a new tab)
- git.kernel.org/stable/c/85397e48afe6be83ffca5ad3f4792296bfc81d3d (opens in a new tab)
- git.kernel.org/stable/c/6c65cf23d4c6170fcf5714c32aa64689718cb142 (opens in a new tab)