CVE-2025-38718 remediation guide

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: sctp: linearize cloned gso packets in sctp_rcv A cloned head skb still shares these frag skbs in fraglist with the original head skb. It's not safe to access these frag skbs. syzbot reported two use-of-uninitialized-memory bugs caused by this: BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211 sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211 sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998 sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88 sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331 sk_b...

Open CVE record

ProductLinux Linux, linux kernel, debian linux

Affected versions>= 90017accff61ae89283ad9a51f9ac46ca01633fb < d0194e391bb493aa6cec56d177b14df6b29188d5, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 03d0cc6889e02420125510b5444b570f4bbf53d5, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < cd0e92bb2b7542fb96397ffac639b4f5b099d0cb, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 4506bcaabe004d07be8ff09116a3024fbd6aa965, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < ea094f38d387d1b0ded5dee4a3e5720aa4ce0139, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 7d757f17bc2ef2727994ffa6d5d6e4bc4789a770, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < fc66772607101bd2030a4332b3bd0ea3b3605250, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 1bd5214ea681584c5886fea3ba03e49f93a43c0e, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < fd60d8a086191fe33c2d719732d2482052fa6805, >= 4.8, >= 4.8 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.6.103, >= 6.7 < 6.12.43, >= 6.13 < 6.15.11, >= 6.16 < 6.16.2, 6.17, 11.0

Fixed versions5.4.297, 5.10.241, 5.15.190, 6.6.103, 6.12.43, 6.15.11, 6.16.2

Priority basisReview · CVSS 7.8 · EPSS 0.16%

Identify the affected asset

Confirm whether Linux Linux, linux kernel, debian linux is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 90017accff61ae89283ad9a51f9ac46ca01633fb < d0194e391bb493aa6cec56d177b14df6b29188d5, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 03d0cc6889e02420125510b5444b570f4bbf53d5, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < cd0e92bb2b7542fb96397ffac639b4f5b099d0cb, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 4506bcaabe004d07be8ff09116a3024fbd6aa965, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < ea094f38d387d1b0ded5dee4a3e5720aa4ce0139, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 7d757f17bc2ef2727994ffa6d5d6e4bc4789a770, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < fc66772607101bd2030a4332b3bd0ea3b3605250, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < 1bd5214ea681584c5886fea3ba03e49f93a43c0e, >= 90017accff61ae89283ad9a51f9ac46ca01633fb < fd60d8a086191fe33c2d719732d2482052fa6805, >= 4.8, >= 4.8 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.6.103, >= 6.7 < 6.12.43, >= 6.13 < 6.15.11, >= 6.16 < 6.16.2, 6.17, 11.0. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.4.297, 5.10.241, 5.15.190, 6.6.103, 6.12.43, 6.15.11, 6.16.2. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.