batman-adv: tp_meter: restrict number of unacked list entries
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 33a3bb4a3345bb511f9c69c913da95d4693e2a4e · < 2233787658db859f0a9b83cb397cf783bb8be865| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's batman-adv tp_meter can let its unacked list grow without bound. An attacker who can send crafted messages to a receiver can cause out-of-memory conditions or waste CPU cycles managing the list. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with batman-adv should check their deployments; affected versions are not specified.