CVE-2026-68315sctp: validate stream count in sctp_process_strreset_inreq()
- 7.5HighCVSS base score
- 0.51%Exploitation in 30 daysEPSS · top 56% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: validate stream count in sctp_process_strreset_inreq() When processing a RESET_IN_REQUEST from a peer, sctp_process_strreset_inreq() derives the stream count from the parameter length but does not check whether the resulting RESET_OUT_REQUEST would exceed SCTP_MAX_CHUNK_LEN. The OUT request header (sctp_strreset_outreq, 16 bytes) is 8 bytes larger than the IN request header (sctp_strreset_inreq, 8 bytes). Generally, the IP payload is bounded to 65535 bytes, so the stream list cannot be large enough to trigger the overflow. However, on interfaces with MTU > 65535 (e.g., loopback with IPv6 jumbograms), a stream list that fits within the incoming IN parameter can cause a __u16 overflow in sctp_make_strreset_req() when computing the OUT request size, leading to an undersized skb allocation and a kernel BUG: net/core/skbuff.c:207 skb_panic net/core/skbuff.c:2625 skb_put net/sctp/sm_make_chunk.c:1535 sctp_addto_chunk net/sctp/sm_make_chunk.c:3695 sctp_make_strreset_req net/sctp/stream.c:655 sctp_process_strreset_inreq The local setsockopt path validates the generated reset request size. However, for an incoming-only reset, it accounts for the smaller IN request even though the peer must generate an OUT request with the same stream list. Such a request cannot be completed successfully by the peer. Reject peer IN requests whose corresponding OUT request would exceed SCTP_MAX_CHUNK_LEN. Also tighten the local check so it does not send an IN request that would require an oversized OUT request from the peer.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.51% · top 56% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 61327d8e7cfb0259d527be17202630f556213249
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 7cf7439948e3bf639119119922c88ec190874ca3
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 60c47dea5d320d2fc706e9aad1db38a04df0a056
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < b255d8cd6cc68045ae9eecbac3b3c14e1f176c9b
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 6f0e39d180cd7cced647381b6fa14fd83d261047
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 1a10fe1aa9c01f41b389a31906a77d538637c9d9
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 00ae679cb21a035491fdad8d58dc6d79cc68b675
- affected 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137 – < 18ae07691d43183d270de8be9dc8e027906015d9
- affected 4.11
- unaffected < 4.11
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/61327d8e7cfb0259d527be17202630f556213249 (opens in a new tab)
- https://git.kernel.org/stable/c/7cf7439948e3bf639119119922c88ec190874ca3 (opens in a new tab)
- https://git.kernel.org/stable/c/60c47dea5d320d2fc706e9aad1db38a04df0a056 (opens in a new tab)
- https://git.kernel.org/stable/c/b255d8cd6cc68045ae9eecbac3b3c14e1f176c9b (opens in a new tab)
- https://git.kernel.org/stable/c/6f0e39d180cd7cced647381b6fa14fd83d261047 (opens in a new tab)
- https://git.kernel.org/stable/c/1a10fe1aa9c01f41b389a31906a77d538637c9d9 (opens in a new tab)
- https://git.kernel.org/stable/c/00ae679cb21a035491fdad8d58dc6d79cc68b675 (opens in a new tab)
- https://git.kernel.org/stable/c/18ae07691d43183d270de8be9dc8e027906015d9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55416 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68315)Record last updated .