CVE-2026-90054
CVE CVE-2026-90054EUVD EUVD-2026-81915Published 2026-09-17T16:05:39.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: tcp: fix corruption of urgent data on multi-segment retransmit On the normal xmit path, while in urgent mode we refuse to build a multi-segment TSO packet, so every segment gets its own urg_ptr: /* tcp_write_xmit() */ limit = mss_now; if (tso_segs > 1 && !tcp_urg_mode(tp)) limit = tcp_mss_split_point(...); The retransmit path has no such guard. __tcp_retransmit_skb() builds a segs > 1 skb and hands it to the GSO layer, which only advances th->seq per segment and copies urg_ptr verbatim: /* __tcp_retransmit_skb() */ len = cur_mss * segs; /* segs > 1, no urg_mode check */ ... /* tcp_gso_segment(): bumps seq only, urg_ptr is copied */ urg_ptr is an offset from the segment's own seq, so a copied value points at a different place on each segment. The receiver rebuilds the absolute urgent seq as seg.seq + urg_ptr, so it walks a moving urgent point instead of the one OOB byte: seg1 seq 1 urg_ptr 5001 -> urgent @ 5001 (ok) seg2 seq 1001 urg_ptr 5001 -> urgent @ 6001 (wrong, +MSS) seg3 seq 2001 urg_ptr 5001 -> urgent @ 7001 (wrong, +2*MSS) The real OOB byte is never pointed at, so the receiver stops splicing it out and delivers it as normal in-band data, corrupting the stream. Guard the retransmit length like the xmit path: keep segs = 1 while in urgent mode.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.18.52; 10d3be569243def8d92ac3722395ef5a59c504e6 <47eb90299e6882d6445672530dd7c51ac33ebdbd; patch: 6.6.157; 10d3be569243def8d92ac3722395ef5a59c504e6 <3d4e005c198dc410ad568f832bffa7569c059ff8; patch: 5.10.270; patch: 0; 4.7; 10d3be569243def8d92ac3722395ef5a59c504e6 <711bfd762bec05fb19bc3b17cbb157c39f4e66da; patch: 5.15.221; 10d3be569243def8d92ac3722395ef5a59c504e6 <ce2b807f42ed5e55567b8864ab72963f90779270; 10d3be569243def8d92ac3722395ef5a59c504e6 <8eb51013b6308870479a64b4a2a018697b997849; patch: 7.2.6; 10d3be569243def8d92ac3722395ef5a59c504e6 <b8f08a94b2a4addc39249dcf9c792e786108621b; 10d3be569243def8d92ac3722395ef5a59c504e6 <ebe55406404f3cb28e36d2b668e2c6c05026ec29; patch: 6.12.110; patch: 7.3-rc1; patch: 6.1.188; 10d3be569243def8d92ac3722395ef5a59c504e6 <4fd2ee4ac154c204d95d8db72221446dac5af9b8
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.