CVE-2026-98549

tcp: prevent collapsing skbs across boundary in rtx queue

  • Critical 9.1

Description

In the Linux kernel, the following vulnerability has been resolved: tcp: prevent collapsing skbs across boundary in rtx queue tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs. The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0. On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it. Both users of the fence are affected: - psp: devices only encrypt skbs with skb->decrypted set. The merged skb keeps decrypted = 0 from the earlier skb, so merged data sent after psp_sock_assoc_set_tx() is retransmitted in cleartext. - tls device offload: the merged skb straddles the start marker set in tls_set_device_offload(). The software fallback (fill_sg_in() returns -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an skb and drop it. Every retransmit rebuilds the same skb, so the connection stalls. Fix this in two places, for defense in depth: 1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence() when tcp_write_queue_tail(sk) is NULL. 2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this condition.

Key facts

Published
18 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.559% likely to be exploited in the next 30 days, higher than 47.256% of CVEs (scores for 18 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.1CVSS 3.1, Criticalfrom the CNA (Linux)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding bf785a303e5faad16439c563826a07cb811856c8 (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 7061aafc680e14e22b191f178b768886475f8524 (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 533344a00ad968181e60d0980c076a9d0de57482 (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 9e2a2f98e8c0197108c6d97a1fa43bfd89071c30 (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 1ae7aee395245874d797890380d9192bd858fb7e (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 7ba87509c54cd519e7ed362e0c85e8431f066a18 (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding 08e835f5ec6e261c79d8c39f8618b3af29e3b0da (affected)
  • e8f69799810c32dd40c6724d829eccc70baad07f up to but excluding fc6d80eb504458d6416b75a94188b268c95c6533 (affected)
LinuxLinux
  • Default status: affected
  • 4.18 (affected)
  • 0 up to but excluding 4.18 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References