Description
In the Linux kernel, the following vulnerability has been resolved: tcp: add accessors to read/set tp->snd_cwnd We had various bugs over the years with code breaking the assumption that tp->snd_cwnd is greater than zero. Lately, syzbot reported the WARN_ON_ONCE(!tp->prior_cwnd) added in commit 8b8a321ff72c ("tcp: fix zero cwnd in tcp_cwnd_reduction") can trigger, and without a repro we would have to spend considerable time finding the bug. Instead of complaining too late, we want to catch where and when tp->snd_cwnd is set to an illegal value.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
5d424d5a674f782d0659a3b66d951f412901faee to < 3308676ec525901bf1656014003c443a60730a04affected5d424d5a674f782d0659a3b66d951f412901faee to < 5aba0ad44fb4a7fb78c5076c313456de199a3c29affected5d424d5a674f782d0659a3b66d951f412901faee to < 41e191fe72282e193a7744e2fc1786b23156c9e4affected5d424d5a674f782d0659a3b66d951f412901faee to < 40570375356c874b1578e05c1dcc3ff7c1322dbeaffected
Linux Linux
Default version status: affected
2.6.17affected0 to < 2.6.17unaffected5.15.47 to ≤ 5.15.*unaffected5.17.15 to ≤ 5.17.*unaffected5.18.4 to ≤ 5.18.*unaffected5.19 to ≤ *unaffected