tcp: avoid too many retransmit packets
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.19
References 8
git.kernel.org
- stable/c/7bb7670f92bfbd05fc41a8f9a8f358b7ffed65f4
- stable/c/d2346fca5bed130dc712f276ac63450201d52969
- stable/c/5d7e64d70a11d988553a08239c810a658e841982
- stable/c/04317a2471c2f637b4c49cbd0e9c0d04a519f570
- stable/c/e113cddefa27bbf5a79f72387b8fbd432a61a466
- stable/c/dfcdd7f89e401d2c6616be90c76c2fac3fa98fde
- stable/c/66cb64a1d2239cd0309f9b5038b05462570a5be1
- stable/c/97a9063518f198ec0adb2ecb89789de342bb8283