CVE-2026-63913

netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check

HIGH
8.2
CVSS Score
Published: July 19, 2026 at 02:55 PM UTC
Updated: October 30, 2026 at 05:55 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 1.0%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.15 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.356.19 ≤ v < 7.0.126.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.932.6.157.19fb9cbb1082d6b31fb45aa1a14432449a0df6cf1
Vendor states this is fixed in 2006979a15af5404bf932a325357683c0bac1656 (fixed)
Vendor states this is fixed in 2bb6d82b586ea5a4cb73bbdd6b7432e96096bc77 (fixed)
Vendor states this is fixed in 6476c17d536dbd321c073242e762ddb2713a1238 (fixed)
Vendor states this is fixed in b98ab51c45c5608a1c19ce7fd17a3032469bb83f (fixed)
Vendor states this is fixed in bed6e04be8e6b9133d8b16d5a42d0e0ce674fa9a (fixed)
Vendor states this is fixed in d67c6adee8d1b65330d0174c4c367faba14e80a8 (fixed)
Vendor states this is fixed in f206def4e86d810f927ba1d8e322ea72b29bce58 (fixed)
Vendor states this is fixed in f5547bebc416d56f56fb5b86dc20aabfa42165a0 (fixed)
Vendor states this is fixed in 2.6.15 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card