Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessOpen TFO connection via sendmsg(MSG_FASTOPEN)
-
DeliveryInject ICMP frag-needed to arm retransmit_skb_hint
-
ExploitTrigger simultaneous open freeing SYN skb
-
ExecutionDangling hint read as rbtree root
-
ImpactKernel use-after-free crash / possible info leak
Vulnerability Assessment
| Exploitation Conditions | Requires the host to use TCP Fast Open: an unprivileged LOCAL process must initiate a TFO connection via sendmsg(MSG_FASTOPEN). The attacker must then deliver a crafted ICMP 'fragmentation needed' message to arm tp->retransmit_skb_hint, and a simultaneous TCP open must free the cloned SYN skb at the head of the retransmit queue while the hint still points at it - the freed skbuff_fclone_cache object is then read during tcp_xmit_retransmit_queue's rbtree walk. Limiting factors: TFO must be in use, the attacker must win the simultaneous-open race and land the ICMP at the right moment, and only kernels in the affected commit range (pre-fix 5.15.x/6.1.x/6.6.x/6.12.x/6.18.x/7.2.x and the 5.11+ line) are vulnerable. Only the demonstrated impact (a UAF read causing a kernel crash) is confirmed by the available sources. |
| Impact | Signals point to a moderate, not emergency, priority. The input CVSS of 8.8 (AV:N/AC:L/PR:N/UI:R) implies a remote, unauthenticated, low-complexity flaw, but the upstream description tells a different story: the trigger is an UNPRIVILEGED LOCAL TFO client calling sendmsg(MSG_FASTOPEN), combined with an attacker-supplied ICMP 'fragmentation needed' message and a race on simultaneous TCP open. CVSS indicates a pure network vector with no privileges, but the description implies a local unprivileged process must participate and that a timing race (simultaneous open) is required - verify reachability with the specific deployment before trusting AV:N/AC:L. The decision label is 'this_week' (not act_now/emergency), consistent with the supporting signals: EPSS is low at 0.16% (5th percentile), there is no CISA KEV listing, and no public exploit is referenced - only the upstream fix commits. The demonstrated impact is a KASAN slab-use-after-free READ used as the root of an rbtree walk (tcp_mark_skb_lost → tcp_simple_retransmit → tcp_v4_err), i.e. a kernel crash / denial-of-service with possible information disclosure, rather than a proven code-execution primitive. Net: a legitimate kernel memory-safety bug worth patching on a normal stable-update cadence, but the 8.8 score likely overstates real-world attacker reach given the local-client and race prerequisites. |
| Exploit ScenarioDerived | An unprivileged local process on the host opens a TCP Fast Open connection via sendmsg(MSG_FASTOPEN); an attacker then delivers a crafted ICMP fragmentation-needed message that arms tp->retransmit_skb_hint, and a simultaneous open frees the cloned SYN skb that the hint still references. The subsequent retransmit-queue walk dereferences the freed skbuff_fclone_cache object, producing a use-after-free read that crashes the kernel (KASAN-detected) and may leak kernel memory. No public exploit is referenced - only the upstream fix commits - and success depends on winning the simultaneous-open race and ICMP timing. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 24, 2026
Kernel crash via a use-after-free read in the Linux kernel TCP retransmission path: tcp_send_synack() frees the cloned SYN skb at the head of the retransmit queue and repairs tp->highest_sack but leaves tp->retransmit_skb_hint pointing at the released skbuff_fclone_cache object, which is later dereferenced during the rbtree walk in tcp_xmit_retransmit_queue(). The assessed vector is local (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H): an unprivileged local process must open a connection using TCP Fast Open (sendmsg(MSG_FASTOPEN)), a crafted ICMP fragmentation-needed message arms the hint, and a simultaneous open must free the armed SYN skb at the right moment - only the resulting UAF read and kernel crash (availability impact) is confirmed by the available sources, with no demonstrated confidentiality or integrity compromise beyond an out-of-bounds read of freed slab memory. No public exploit code was identified at time of analysis, EPSS is low at 0.16% (5th percentile), and the issue is not in CISA KEV; vendor patches ship in the 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 and 7.3-rc5 stable releases.
RemediationAI
Apply the vendor-released stable fixes: Linux 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 and 7.3-rc5, each of which carries the change that synchronises tp->retransmit_skb_hint to the replacement SYN skb in tcp_send_synack(); the individual stable commits are listed in the NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-98374), e.g. https://git.kernel.org/stable/c/c5b4da1f403a658c1c19766be2b426003ada419f for the 5.15 branch - verify your distribution has picked up the equivalent backport before treating a host as fixed. Where an immediate kernel update is not possible, the trigger path described in the available sources requires TCP Fast Open, so hosts that do not rely on it can set net.ipv4.tcp_fastopen=0 (and avoid per-socket MSG_FASTOPEN use) to remove the arming step, accepting the loss of TFO's connection-setup latency benefit and the need to re-enable it once patched; this is a compensating control only and does not fix the dangling hint, which the upstream change addresses. No public exploit code was identified at time of analysis, so prioritisation can follow normal patch cadence rather than emergency response.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in the TCP transmit/retransmit bookkeeping of the Linux kernel. When tcp_send_synack() replaces the cloned SYN skb at the head of the retransmit (rtx) queue with a copy, it unlinks and frees the original through tcp_rtx_queue_unlink_and_free() and only re-synchronises tp->highest_sack; tp->retransmit_skb_hint is left dangling at the freed object, which comes from the skbuff_fclone_cache slab. Any later read of that hint - tcp_verify_retransmit_hint() and the rbtree traversal rooted at the hint in tcp_xmit_retransmit_queue() - touches freed memory, producing the reported KASAN slab-use-after-free in tcp_mark_skb_lost (net/ipv4/tcp_input.c:1316), reached via tcp_simple_retransmit and tcp_v4_err on an ICMP error path. The trigger sequence requires TCP Fast Open to be in use, an attacker-supplied ICMP fragmentation-needed message to arm the hint, and a simultaneous open to free the armed SYN skb; the fix synchronises the hint to the replacement copy. No CWE identifier is supplied in the source data; the defect class is a use-after-free (dangling pointer) in the IPv4 TCP error-handling/simultaneous-open interaction. The stale pointer is only reachable on kernels within the affected commit range (introduced by commit c31b70c9968f on the 5.11+ line), and the practical preconditions - TFO in use, a won simultaneous-open race, and correctly timed ICMP delivery - make exploitation timing-dependent and non-trivial, which is reflected in the AC:H assessment.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Trigger requires a local unprivileged TFO client (PR:L, AV:L) and a simultaneous-open/ICMP race (AC:H); confirmed impact is a kernel UAF read causing a crash (A:H) with limited potential leak (C:L).
Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).
CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Lifecycle Timeline
4DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack()
When tcp_send_synack() replaces the cloned SYN skb at the head of the retransmit queue with a copy, it frees the original with tcp_rtx_queue_unlink_and_free() and only repairs tp->highest_sack. tp->retransmit_skb_hint keeps pointing at the freed skbuff_fclone_cache object.
The dangling hint is read in tcp_verify_retransmit_hint() and used as the root of the rbtree walk in tcp_xmit_retransmit_queue(). An unprivileged TFO client (sendmsg(MSG_FASTOPEN)) can arm the hint with an attacker-supplied ICMP fragmentation-needed message, after which a simultaneous open frees the armed SYN skb:
BUG: KASAN: slab-use-after-free in tcp_mark_skb_lost (net/ipv4/tcp_input.c:1316) Read of size 4 at addr ffff88800604d928 by task swapper/1/0 Call Trace: tcp_mark_skb_lost (net/ipv4/tcp_input.c:1316) tcp_simple_retransmit (net/ipv4/tcp_input.c:3158) tcp_v4_err (net/ipv4/tcp_ipv4.c:587)
Sync the hint to the copy.
Executive ViewAI
A high-severity vulnerability in the Linux kernel's TCP retransmission path could allow an unprivileged local user to crash the kernel, causing service disruption. While exploitation requires precise timing and specific conditions, a successful attack could lead to denial-of-service, impacting system availability. Leadership should prioritize patching to maintain service uptime and security posture.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-94323
GHSA-2q84-vc4j-mp23
NVD
CVE.org
EPSS
Exploit-DB