CVE-2026-99283
Received Received - Intake

TCP Timeout Misconfiguration in Linux Kernel

Vulnerability report for CVE-2026-99283, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-07

Last updated on: 2026-11-07

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-07
Last Modified
2026-11-07
Generated
2026-11-07
AI Q&A
2026-11-07
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves the netfilter connection tracking system mishandling TCP Reset (RST) packets. When an RST packet does not match the expected sequence number, the connection tracking entry remains in an ESTABLISHED state instead of closing. However, the system incorrectly applies a short 10-second timeout (CLOSE timeout) to these entries, causing them to expire prematurely while the actual TCP connections remain active. This can lead to stale connection tracking entries.

Detection Guidance

This vulnerability affects the Linux kernel's netfilter connection tracking (conntrack) for TCP connections. Detection requires checking kernel logs for connection tracking anomalies or unexpected TCP RST packet handling. Monitor for conntrack entries expiring prematurely despite active connections. Use commands like 'dmesg | grep conntrack' or 'conntrack -L' to inspect connection states and timeouts.

Impact Analysis

This vulnerability may cause network disruptions by prematurely terminating valid TCP connections tracked by the Linux kernel's connection tracking system. It can lead to unexpected connection drops, degraded network performance, or service outages for applications relying on stable TCP connections.

Mitigation Strategies

Apply the latest Linux kernel patches addressing this issue. Update to a kernel version containing the fix for commit be0502a3f2e9. Monitor network traffic for unusual RST packet patterns. Consider temporarily disabling conntrack for TCP if the issue is critical until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-99283. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...