sctp: prevent peer transport count overflow
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.8epss 0.5%
from disclosure to weapon35 days
Published on NVDAug 15
1st PoC+35d
exploitation probability
0.5%top 60% of all CVEs
observed exploitation
nono source reports it
2 public exploit(s)
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · Linuxpublic PoCs found — 2
githubgithub.com/HORKimhab/CVE-2026-74469★ 0githubgithub.com/0xBlackash/CVE-2026-74469★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://git.kernel.org/stable/c/09e722030e8148ba4ed1e42c6b2ea57bda9f9895https://git.kernel.org/stable/c/4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0https://git.kernel.org/stable/c/546221b86ceeba0d8fec92d46a0604bb7b62be07https://git.kernel.org/stable/c/6201cd1d70f1670c5b31ac506e7ab2fa7b8e7f75https://git.kernel.org/stable/c/80f48523a0fe42db2e7375dff4e38a25c117090ahttps://git.kernel.org/stable/c/b453e00da1211e997b82743d28af7714c59c05c8https://git.kernel.org/stable/c/bd0e9289e2642f6a5c54faad304ce0f41e926d22https://git.kernel.org/stable/c/dfea32dd76f390e3155177b0038cc47b01386198