Kernel data exposure and crash via shared fragments
Published Sep 4, 2025 · Updated Aug 5, 2026
Use of uninitialized memory in Linux kernel SCTP allows local users to expose kernel data or crash the system through local traffic. In sctp_rcv(), a cloned GSO head packet continues sharing frag_list skbs with the original, but the receive path accesses and mutates those shared fragments without first linearizing the clone. Reachability requires a local user to generate SCTP GSO traffic and a packet clone; the resulting kernel-memory exposure, metadata corruption, or panic stays on the host.
Summary
What happened
Use of uninitialized memory in Linux kernel SCTP allows local users to expose kernel data or crash the system through local traffic. In sctp_rcv(), a cloned GSO head packet continues sharing frag_list skbs with the original, but the receive path accesses and mutates those shared fragments without first linearizing the clone. Reachability requires a local user to generate SCTP GSO traffic and a packet clone; the resulting kernel-memory exposure, metadata corruption, or panic stays on the host.
The record
- CVE
- CVE-2025-38718
- Published
- Sep 4, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.8
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <03d0cc6889e02420125510b5444b570f4bbf53d5
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <1bd5214ea681584c5886fea3ba03e49f93a43c0e
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <4506bcaabe004d07be8ff09116a3024fbd6aa965
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <7d757f17bc2ef2727994ffa6d5d6e4bc4789a770
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <cd0e92bb2b7542fb96397ffac639b4f5b099d0cb
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <d0194e391bb493aa6cec56d177b14df6b29188d5
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <ea094f38d387d1b0ded5dee4a3e5720aa4ce0139
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <fc66772607101bd2030a4332b3bd0ea3b3605250
- Affected versionversion=90017accff61ae89283ad9a51f9ac46ca01633fb <fd60d8a086191fe33c2d719732d2482052fa6805
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo