tcp: avoid too many retransmit packets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b701a99e431db784714c32fc6b68123045714679 · < dfcdd7f89e401d2c6616be90c76c2fac3fa98fde| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tcp: avoid too many retransmit packets
If a TCP socket is using TCP_USER_TIMEOUT, and the other peer retracted its window to zero, tcp_retransmit_timer() can retransmit a packet every two jiffies (2 ms for HZ=1000), for about 4 minutes after TCP_USER_TIMEOUT has 'expired'.
The fix is to make sure tcp_rtx_probe0_timed_out() takes icsk->icsk_user_timeout into account.
Before blamed commit, the socket would not timeout after icsk->icsk_user_timeout, but would use standard exponential backoff for the retransmits.
Also worth noting that before commit e89688e3e978 ("net: tcp: fix unexcepted socket die when snd_wnd is 0"), the issue would last 2 minutes instead of 4.
From the CVE record · Linux
The Linux kernel's TCP retransmission timer can send a packet every two jiffies for about four minutes after TCP_USER_TIMEOUT expires. This occurs when a TCP socket uses TCP_USER_TIMEOUT and the other network peer retracts its window to zero. The peer can trigger excessive retransmissions under those conditions; the input does not specify authentication or user-interaction requirements.
Teams running the Linux kernel should check their systems; affected versions are not specified.