sctp: prevent peer transport count overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8f840e47f190cbe61a96945c13e9551048d42cef · < 4ba5bf7ed50f235ea4581de8e7a0002f4ed287b0| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s SCTP peer count can wrap to zero when an association adds its 65,536th unique peer. If an SCTP diagnostic dump then runs, it can write 8 MiB of peer addresses beyond the allocated buffer. The input does not specify how an attacker could trigger these conditions or whether authentication or user interaction is required.
Engineers running Linux kernels with SCTP should check their versions; affected versions are not specified in the input.