sctp: fix stream->outcnt underflow on duplicate RECONF responses
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 11ae76e67a179f25ae8f772d62a7ddf717b1cdf3 · < d02a5794c3deedcb8476d017fcee2b7aaedab2e1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix stream->outcnt underflow on duplicate RECONF responses
A cached RECONF chunk may contain more than one request parameter. A duplicate response can therefore find and process the same ADD_OUT request again while another parameter is still outstanding, rolling back outcnt twice and possibly underflowing it.
Track outstanding request types as bits and clear each bit after its first response. Later responses for the same request are then ignored.
From the CVE record · Linux
The Linux kernel’s SCTP handling can process the same ADD_OUT request twice when a duplicate RECONF response arrives while another request parameter remains outstanding. This can underflow the stream’s outgoing count. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels with SCTP should check their exposure; affected versions are not specified.