CVE Tools

CVE-2026-52931

batman-adv: tp_meter: avoid use of uninit sender vars

No known exploitation. EPSS puts it in the 33rd percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, < 0e388af04b3958b178a1b979527f93eb46ea1feeUpgrade to: 0e388af04b3958b178a1b979527f93eb46ea1feeAffected: ≥ 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, < 1a21c055f66e78973712a4a1be2a554f1ee2e4f4Upgrade to: 1a21c055f66e78973712a4a1be2a554f1ee2e4f4Affected: ≥ 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, < 9884c9c02d3c90e9215db3c5128f59045d20ae91Upgrade to: 9884c9c02d3c90e9215db3c5128f59045d20ae91Affected: ≥ 33a3bb4a3345bb511f9c69c913da95d4693e2a4e, < 53f931e0146ae5bdab4cba302646827d06b3794bUpgrade to: 53f931e0146ae5bdab4cba302646827d06b3794b + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS33rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 33rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 117 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. OpenVAS check added
  4. Patch availablerecord updated
  5. Record updated
  6. Record updated

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.