sctp: avoid livelock while updating retransmit path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 · < c9338057df1025f578fe7d0ff08bada87b8b838d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: avoid livelock while updating retransmit path
sctp_assoc_update_retran_path() can loop forever when every remaining transport, including retran_path, is SCTP_UNCONFIRMED: the state check runs before the wraparound test, so the loop cannot observe that it has completed a full pass.
Fix this by considering a transport only when it is not UNCONFIRMED, then checking whether the walk has returned to retran_path. This makes the full-pass termination independent of the transport state while preserving the existing fallback selection semantics.
Also restore the NULL guard around the retran_path assignment. In the all-UNCONFIRMED case there is no eligible replacement transport, and installing NULL would leave later retransmit-path users and the debug print with a NULL path.
From the CVE record · Linux
The Linux kernel’s SCTP retransmit-path update can loop forever when every remaining transport, including the current retransmit path, is unconfirmed. The input does not specify how this condition can be triggered or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.