netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9fb9cbb1082d6b31fb45aa1a14432449a0df6cf1 · < b98ab51c45c5608a1c19ce7fd17a3032469bb83f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check
An unintended behavior in the TCP conntrack state machine allows a connection to be forced into the CLOSE state using an RST packet with an invalid sequence number.
Specifically, after a SYN packet is observed, an RST with an invalid SEQ can transition the conntrack entry to TCP_CONNTRACK_CLOSE, regardless of whether the RST corresponds to the expected reply direction. The relevant code path assumes the RST is a response to an outgoing SYN, but does not validate packet direction or ensure that a matching SYN was actually sent in the opposite direction.
As a result, a crafted packet sequence consisting of a SYN followed by an invalid-sequence RST can prematurely terminate an active NAT entry. This makes connection teardown easier than intended.
So, tighten the state transition logic to ensure that RST-triggered CLOSE transitions only occur when the RST is a valid response to a previously observed SYN in the correct direction.
From the CVE record · Linux
The Linux kernel's TCP conntrack state machine can move a connection to CLOSE after observing a SYN followed by an invalid-sequence RST, without checking that the RST is a reply in the correct direction. An attacker able to send that crafted packet sequence can prematurely terminate an active NAT entry. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels that use TCP conntrack should check their versions against the Linux vendor advisory; affected versions are not specified.