tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5d424d5a674f782d0659a3b66d951f412901faee · < 90385f2b65d0cd2b3b1ac8909f0cc6dd31062cfc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd
syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing.
tcp_mtu_probe() has checks about starting an MTU probe if tcp_snd_cwnd(tp) >= 11.
But nothing prevents tcp_snd_cwnd(tp) to be reduced later and before the MTU probe succeeds.
This bug would lead to potential zero-divides.
Debugging added in commit 40570375356c ("tcp: add accessors to read/set tp->snd_cwnd") has paid off :)
While we are at it, address potential overflows in this code.
From the CVE record · Linux
The Linux kernel’s TCP MTU probing code can encounter a divide-by-zero if the send congestion window shrinks after a probe starts but before it succeeds. The input does not establish how an attacker could trigger this condition, whether authentication or user interaction is needed, or its resulting impact.
Engineers running the Linux kernel should check their builds; affected versions are not specified.