tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2f487712b89376fce267223bbb0db93d393d4b09 · < 1b6f13f626665cac67ba5a012765427680518711| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG
The GRP_ACK_MSG handler in tipc_group_proto_rcv() currently decrements bc_ackers on every inbound group ACK, even when the same member has already acknowledged the current broadcast round.
Because bc_ackers is a u16, a duplicate ACK received after the last legitimate ACK wraps the counter to 65535. Once wrapped, tipc_group_bc_cong() keeps reporting congestion and later group broadcasts on the affected socket stay blocked until the group is recreated.
Fix this by ignoring duplicate or stale ACKs before touching bc_acked or bc_ackers. This makes repeated GRP_ACK_MSG handling idempotent and prevents the underflow path.
From the CVE record · Linux
The Linux kernel TIPC group ACK handler decrements its acknowledgment counter for duplicate ACKs. If a duplicate ACK arrives after the last legitimate ACK, the counter wraps, causing later group broadcasts on the affected socket to remain blocked until the group is recreated. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with TIPC should check their versions against the vendor advisory; affected versions were not provided.