Stream corruption via copied TCP urgent pointers
Published Sep 17, 2026 · Updated Sep 17, 2026
Urgent-data corruption in Linux 4.7 TCP allows remote attackers to corrupt received streams via multi-segment retransmissions. In __tcp_retransmit_skb(), urgent-mode packets are not restricted to one segment, and tcp_gso_segment() copies urg_ptr without adjusting it for each segment's sequence number. Exposure requires outgoing TCP urgent data and multi-segment retransmission; the receiver then delivers the out-of-band byte as ordinary in-band data.
Summary
What happened
Urgent-data corruption in Linux 4.7 TCP allows remote attackers to corrupt received streams via multi-segment retransmissions. In __tcp_retransmit_skb(), urgent-mode packets are not restricted to one segment, and tcp_gso_segment() copies urg_ptr without adjusting it for each segment's sequence number. Exposure requires outgoing TCP urgent data and multi-segment retransmission; the receiver then delivers the out-of-band byte as ordinary in-band data.
The record
- CVE
- CVE-2026-90054
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <3d4e005c198dc410ad568f832bffa7569c059ff8
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <47eb90299e6882d6445672530dd7c51ac33ebdbd
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <4fd2ee4ac154c204d95d8db72221446dac5af9b8
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <711bfd762bec05fb19bc3b17cbb157c39f4e66da
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <8eb51013b6308870479a64b4a2a018697b997849
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <b8f08a94b2a4addc39249dcf9c792e786108621b
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <ce2b807f42ed5e55567b8864ab72963f90779270
- Affected versionversion=10d3be569243def8d92ac3722395ef5a59c504e6 <ebe55406404f3cb28e36d2b668e2c6c05026ec29
- Affected versionversion=4.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started