CVE-2026-68118tcp: challenge ACK for non-exact RST in SYN-RECEIVED
- 8.2HighCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: tcp: challenge ACK for non-exact RST in SYN-RECEIVED The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK. RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped. Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing order. Factor the per-netns challenge ACK quota out of tcp_send_challenge_ack() so request sockets can share it. Use the request socket's send_ack() callback and its own out-of-window ACK timestamp to send and rate-limit the response.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| NVDNVD · Received | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.50% · top 57% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < c5dc463cc60eb26079b19607c9dbda76491dad05
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < 8b0a3a094f4cae2fb92e4d08d4eef7246a9d9c49
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < 0fe4636665d14a258de70b4f3e8248e6d42038f1
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < 234f9ffbd9b2c1b24ec67200ea3cff07401bec48
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < 22cec809b048495310f206d9abbcdbbfbdce3ae3
- affected 282f23c6ee343126156dd41218b22ece96d747e3 – < a28c4fcbf774e23b4779cae468e3497a5ad1f4a1
- affected 86791bbfe5ed7b275be040cfeff049a1624af1b7
- affected 61f69dc4e40e41b0018f00fa4aeb23d3239556fb
- affected 34fb350281ced2a72707a5c0064f69992d440edb
- affected 3.0.58 – < 3.1
- affected 3.2.37 – < 3.3
- affected 3.4.25 – < 3.5
- affected 3.6
- unaffected < 3.6
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.153 – ≤ 6.6.*
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/c5dc463cc60eb26079b19607c9dbda76491dad05 (opens in a new tab)
- https://git.kernel.org/stable/c/8b0a3a094f4cae2fb92e4d08d4eef7246a9d9c49 (opens in a new tab)
- https://git.kernel.org/stable/c/0fe4636665d14a258de70b4f3e8248e6d42038f1 (opens in a new tab)
- https://git.kernel.org/stable/c/234f9ffbd9b2c1b24ec67200ea3cff07401bec48 (opens in a new tab)
- https://git.kernel.org/stable/c/22cec809b048495310f206d9abbcdbbfbdce3ae3 (opens in a new tab)
- https://git.kernel.org/stable/c/a28c4fcbf774e23b4779cae468e3497a5ad1f4a1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55499 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68118)Record last updated .