CVE-2026-63834

batman-adv: tp_meter: restrict number of unacked list entries

N/A
Published: July 19, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:17 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: tp_meter: restrict number of unacked list entries When the unacked_list is unbound, an attacker could send messages with small lengths and appropriated seqno + gaps to force the receiver to allocate more and more unacked_list entries. And the end either causing an out-of-memory situation or increase the management overhead for the (large) list that significant portions of CPU cycles are wasted in searching through the list. When limiting the list to a specific number, it is important to still correctly add a new entry to the list. But if the list became larger than the limit, the last entry of the list (with the highest seqno) must be dropped to still allow the earlier seqnos to finish and therefore to continue the process. Otherwise, the process might get stuck with too high seqnos which are not handled by batadv_tp_ack_unordered().

Affected

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

4.8 ≤ v < 5.10.2604.8 ≤ v < 5.15.2114.8 ≤ v < 6.1.1774.8 ≤ v < 6.12.954.8 ≤ v < 6.18.384.8 ≤ v < 6.6.1444.8 ≤ v < 7.1.34.8 ≤ v < 7.233a3bb4a3345bb511f9c69c913da95d4693e2a4e4.8
Vendor states this is fixed in 1111a3381bca2d1f084a07686bc783af5ab23df7 (fixed)
Vendor states this is fixed in 1c616b0be4bd8399d485e25e91859373b95d6013 (fixed)
Vendor states this is fixed in 1fb8762600a393d1caccd63be5d07e1756982d68 (fixed)
Vendor states this is fixed in 2233787658db859f0a9b83cb397cf783bb8be865 (fixed)
Vendor states this is fixed in 31a88792bfba142be3c9521538c1db805677381f (fixed)
Vendor states this is fixed in c6231d628d06d841bc1617b2f7034f5f39876b16 (fixed)
Vendor states this is fixed in e7c775110e1858e5a7471a23a9c9658c0af9df89 (fixed)
Vendor states this is fixed in f8c499fd275e59203b77fca76ae6ef2d096c2133 (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.260 (unaffected)
Vendor states this is fixed in 5.15.211 (unaffected)
Vendor states this is fixed in 6.1.177 (unaffected)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (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

StatusAWAITING ANALYSIS

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