tipc: prevent snt_unacked underflow on CONN_ACK
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 10724cc7bb7832b482df049c20fd824d928c5eaa · < 3cfa3d8e0dc167850edeb5bf5a07757db83fd54e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tipc: prevent snt_unacked underflow on CONN_ACK
tipc_sk_conn_proto_rcv() subtracts the peer-supplied connection ack count from the unsigned 16-bit send counter snt_unacked without checking that it does not exceed the number of messages actually outstanding:
tsk->snt_unacked -= msg_conn_ack(hdr);
msg_conn_ack() is read straight from a received CONN_MANAGER/CONN_ACK message. If the ack count is larger than snt_unacked, the subtraction wraps to a near-maximum value, leaving tsk_conn_cong() permanently true and starving the connection of further transmits.
Validate the ACK count at the start of the CONN_ACK block and drop the message if it acknowledges more messages than are outstanding. A peer (or, for a local connection, the connected peer socket) can otherwise wedge a TIPC connection's send side by sending an oversized connection ack.
From the CVE record · Linux
The Linux kernel’s TIPC connection handler does not check whether a received connection ACK acknowledges more messages than are outstanding. A peer, or the connected peer socket for a local connection, can send an oversized ACK that prevents further transmissions on that connection. No user interaction is described.
Engineers running Linux systems that use TIPC should check whether their kernel is affected; affected versions are not specified.