batman-adv: tt: avoid request storms during pending request
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 335fbe0f5d2501b7dd815806aef6fd9bad784eb1 · < 6a65ac8a81e903bb4b555c1d13532f5cb0167a4a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: avoid request storms during pending request
batadv_send_tt_request() allocates a tt_req_node when none exists for the destination originator node. This should prevent that a multiple TT requests are send at the same time to an originator.
But if allocation of the send buffer failed, this request must be cleaned up again. But indicator for such a failure is "ret == false". But the actual implementation is checking for "ret == true".
The check must be inverted to not loose the information about the TT request directly after it was attempted to be sent out. This should avoid potential request storms.
From the CVE record · Linux
The Linux kernel’s batman-adv TT request handling fails to clean up a pending request when send-buffer allocation fails. This can lead to request storms; the input does not specify how an attacker could trigger the issue, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with batman-adv should check their deployments; affected versions are not specified.