Description
In the Linux kernel, the following vulnerability has been resolved:

netfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets

Commit be0502a3f2e9 ("netfilter: conntrack: tcp: only close if RST
matches exact sequence") keeps an established conntrack entry in
ESTABLISHED when an in-window RST does not match the expected sequence
number exactly, so the endpoint can validate the RST with a challenge
ACK.

The timeout selection nevertheless uses the CLOSE timeout for every RST
packet. The bug is that timeout selection is based on the packet type,
not on the state transition result: even when RST validation keeps
new_state in ESTABLISHED, the timeout is still forced to
TCP_CONNTRACK_CLOSE.

Linux TCP independently rate limits challenge ACKs per socket. A second
non-exact RST can therefore arrive after the first challenge ACK has
restored the timeout but before the rate limit expires. The second RST
lowers the timeout to 10 seconds again while the endpoint suppresses the
second challenge ACK, allowing the conntrack entry to expire while both
TCP endpoints remain established.

Using the ESTABLISHED timeout for such RSTs would avoid this short
expiration window, but it could also retain stale entries for the
five-day default because conntrack cannot reliably match the endpoint's
exact TCP state.

Use the UNACK timeout for RST packets that leave the conntrack entry in
TCP_CONNTRACK_ESTABLISHED. Exact-match RSTs and accepted RST packet
trains still fall through to timeouts[new_state], which preserves the
CLOSE timeout when conntrack accepts the RST as closing the flow.

This avoids the aggressive 10-second expiration window for non-exact
RSTs while preserving the short timeout for RSTs that conntrack accepts
as closing the flow.
Published: 2026-11-07
Score: n/a
EPSS: n/a
KEV: No
Impact: Denial of Service (TCP Connection Loss)
Action: Apply Update
AI Analysis

Impact

The Linux kernel conntrack module incorrectly assigns the CLOSE timeout to any RST packet, even when the packet does not cause a state transition out of ESTABLISHED. This behavior creates a short 10‑second expiration window for established connections that can be prematurely triggered by crafted non‑exact RST packets, leading to the unexpected loss of legitimate network traffic.

Affected Systems

Affected systems are Linux kernel installations that have not yet integrated the commit adding the UNACK timeout handling for non‑closing RSTs. Because no specific version range is provided, any kernel older than that commit is vulnerable. The issue occurs in the generic Linux kernel distribution and affects all network stacks relying on the conntrack subsystem.

Risk and Exploitability

Based on the description, it is inferred that an attacker with remote network connectivity could send crafted non‑exact RST packets to exploit the timeout bug and cause a denial‑of‑service. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, and no public exploit has been reported, suggesting moderate risk. The likely attack vector is remote network exploitation, and the vulnerability would require only network access to the target host.

Generated by OpenCVE AI on November 7, 2026 at 21:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes the commit which correctly applies the UNACK timeout to non‑closing RST packets.
  • Configure firewall or packet filtering rules to drop or rate‑limit suspicious RST packets originating from untrusted sources to reduce the chance of triggering the timeout bug.
  • Regularly inspect conntrack tables and system logs for premature expiration of established connections, which may indicate an attempted exploitation of this flaw.

Generated by OpenCVE AI on November 7, 2026 at 21:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 07 Nov 2026 22:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-668

Sat, 07 Nov 2026 22:00:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Sat, 07 Nov 2026 20:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets Commit be0502a3f2e9 ("netfilter: conntrack: tcp: only close if RST matches exact sequence") keeps an established conntrack entry in ESTABLISHED when an in-window RST does not match the expected sequence number exactly, so the endpoint can validate the RST with a challenge ACK. The timeout selection nevertheless uses the CLOSE timeout for every RST packet. The bug is that timeout selection is based on the packet type, not on the state transition result: even when RST validation keeps new_state in ESTABLISHED, the timeout is still forced to TCP_CONNTRACK_CLOSE. Linux TCP independently rate limits challenge ACKs per socket. A second non-exact RST can therefore arrive after the first challenge ACK has restored the timeout but before the rate limit expires. The second RST lowers the timeout to 10 seconds again while the endpoint suppresses the second challenge ACK, allowing the conntrack entry to expire while both TCP endpoints remain established. Using the ESTABLISHED timeout for such RSTs would avoid this short expiration window, but it could also retain stale entries for the five-day default because conntrack cannot reliably match the endpoint's exact TCP state. Use the UNACK timeout for RST packets that leave the conntrack entry in TCP_CONNTRACK_ESTABLISHED. Exact-match RSTs and accepted RST packet trains still fall through to timeouts[new_state], which preserves the CLOSE timeout when conntrack accepts the RST as closing the flow. This avoids the aggressive 10-second expiration window for non-exact RSTs while preserving the short timeout for RSTs that conntrack accepts as closing the flow.
Title netfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-11-07T20:14:11.433Z

Reserved: 2026-09-25T10:25:14.405Z

Link: CVE-2026-99283

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-07T21:17:00.477

Modified: 2026-11-07T21:17:00.477

Link: CVE-2026-99283

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-07T22:00:18Z

Weaknesses
  • CWE-668

    Exposure of Resource to Wrong Sphere