Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90054: tcp: fix corruption of urgent data on multi-segment retransmit

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 3d4e005c198dc410ad568f832bffa7569c059ff8, 47eb90299e6882d6445672530dd7c51ac33ebdbd, 4fd2ee4ac154c204d95d8db72221446dac5af9b8.

Low priority for now. Upgrade to Linux Linux 3d4e005c198dc410ad568f832bffa7569c059ff8, 47eb90299e6882d6445672530dd7c51ac33ebdbd, 4fd2ee4ac154c204d95d8db72221446dac5af9b8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90054

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.7affected
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before 8eb51013b6308870479a64b4a2a018697b997849affected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before 711bfd762bec05fb19bc3b17cbb157c39f4e66daaffected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before 3d4e005c198dc410ad568f832bffa7569c059ff8affected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before 4fd2ee4ac154c204d95d8db72221446dac5af9b8affected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before ebe55406404f3cb28e36d2b668e2c6c05026ec29affected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before b8f08a94b2a4addc39249dcf9c792e786108621baffected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before 47eb90299e6882d6445672530dd7c51ac33ebdbdaffected · git
    • 10d3be569243def8d92ac3722395ef5a59c504e6 and later · before ce2b807f42ed5e55567b8864ab72963f90779270affected · git
    • before 4.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90051Sep 17, 2026 · tcp: reject non zerocopy devmem tx
    31Monitor
  • ← EarlierCVE-2026-90053Sep 17, 2026 · net/sched: sch_htb: limit htb_classify inner-class filter hops
    0Monitor
  • Later →CVE-2026-90055Sep 17, 2026 · usb: atm: usbatm: fix invalid ci_range initialization
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3d4e005c198dc410ad568f832bffa7569c059ff8Vendor (CNA)
Linux Linux47eb90299e6882d6445672530dd7c51ac33ebdbdVendor (CNA)
Linux Linux4fd2ee4ac154c204d95d8db72221446dac5af9b8Vendor (CNA)
Linux Linux711bfd762bec05fb19bc3b17cbb157c39f4e66daVendor (CNA)
Linux Linux8eb51013b6308870479a64b4a2a018697b997849Vendor (CNA)
Linux Linuxb8f08a94b2a4addc39249dcf9c792e786108621bVendor (CNA)
Linux Linuxce2b807f42ed5e55567b8864ab72963f90779270Vendor (CNA)
Linux Linuxebe55406404f3cb28e36d2b668e2c6c05026ec29Vendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records