tcp: exclude old ACKs from tcp fast path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 31770e34e43d6c8dee129bfee77e56c34e61f0e5 · < ff037920c688ae6ca1153fec01e90e6782712455| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tcp: exclude old ACKs from tcp fast path
Exclude old ACKs before SND.UNA from the tcp fast path as well as ACKs after SND.NXT.
Such ACKs will fall through to the slow path, where tcp_ack() performs the appropriate validation and challenge ACK handling according to RFC5961 and Commit 3d501dd326fb1c7 ("tcp: do not accept ACK of bytes we never sent").
This prevents old ACKs from being accepted or modifying connection state as part of the fast path before appropriate ACK validation is applied. In particular, this prevents payload carried by a segment with an excessively old ACK from advancing RCV.NXT before the ACK is rejected.
From the CVE record · Linux
The Linux kernel TCP fast path can process an excessively old ACK before validating it. A network segment carrying such an ACK and payload can advance RCV.NXT before the ACK is rejected. The input does not specify authentication or user-interaction requirements.
Teams running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.