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.
Published: 2026-10-18
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Potential clear‑text transmission of encrypted data and connection stalls
Action: Patch Immediately
AI Analysis

Impact

The vulnerability in the Linux kernel’s TCP stack allows an attacker to cause two distinct skbs—one already queued for transmission and another added after a switch to device or TLS encryption—to be merged during retransmission or selective acknowledgment processing. The merge removes the encrypted flag from the later skb, resulting in that data being sent in cleartext. In configurations that use TLS offload drivers such as mlx5, nfp, or funeth, the merged skb spans the TLS start marker and cannot be handled by the software fallback or hardware offload, causing every retransmission to fail and the connection to stall. This flaw corresponds to the weakness described by CWE‑319, Cleartext Transmission over a Network.

Affected Systems

The flaw affects all Linux kernel builds that implement the described TCP write queue and retransmission logic, particularly systems employing device encryption that only encrypt skbs marked as 'decrypted' and those using TLS offload drivers. Because no specific kernel version is cited, any actively deployed kernel that supports these features is potentially impacted.

Risk and Exploitability

The CVSS score of 9.1 indicates high severity, while the EPSS score is reported as <1%, suggesting a low probability of exploitation under current conditions. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is inferred to manipulation of TCP traffic that induces a retransmission or SACK shift—either from a nearby network actor or a compromised host—since the flaw is triggered during the kernel handling of retransmitted packets. While the impact includes privacy exposure and denial of service, the limited exploitation probability and lack of known active exploits imply that the immediate risk is moderate.

Generated by OpenCVE AI on October 24, 2026 at 15:42 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the two fix paths which fall back to tcp_rtx_queue_tail when tcp_write_queue_tail is null and check that decrypted flags match before collapsing skbs
  • Restart networking components or reboot the system so the updated kernel is fully in use
  • If an immediate kernel upgrade is not possible, disable hardware encryption or TLS offload drivers, or configure network devices to avoid sending data after an encryption switch until the patch is applied

Generated by OpenCVE AI on October 24, 2026 at 15:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Fri, 30 Oct 2026 12:45:00 +0000


Sat, 24 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L'}

cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H'}


Wed, 21 Oct 2026 13:15:00 +0000


Tue, 20 Oct 2026 20:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-310

Tue, 20 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-319
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L'}

threat_severity

Moderate


Sun, 18 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-310

Sun, 18 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
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.
Title tcp: prevent collapsing skbs across boundary in rtx queue
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:38:24.928Z

Reserved: 2026-09-25T10:25:14.356Z

Link: CVE-2026-98549

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:06.913

Modified: 2026-10-30T13:21:15.940

Link: CVE-2026-98549

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98549 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T15:45:07Z

Weaknesses
  • CWE-319

    Cleartext Transmission of Sensitive Information