sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9ed7bfc79542119ac0a9e1ce8a2a5285e43433e9 · < 68ba44639537de6f91fe32783766322d41848127| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop
With this refcnt added in sctp_stream_priorities, we don't need to traverse all streams to check if the prio is used by other streams when freeing one stream's prio in sctp_sched_prio_free_sid(). This can avoid a nested loop (up to 65535 * 65535), which may cause a stuck as Ying reported:
watchdog: BUG: soft lockup - CPU#23 stuck for 26s! [ksoftirqd/23:136] Call Trace: <TASK> sctp_sched_prio_free_sid+0xab/0x100 [sctp] sctp_stream_free_ext+0x64/0xa0 [sctp] sctp_stream_free+0x31/0x50 [sctp] sctp_association_free+0xa5/0x200 [sctp]
Note that it doesn't need to use refcount_t type for this counter, as its accessing is always protected under the sock lock.
v1->v2: - add a check in sctp_sched_prio_set to avoid the possible prio_head refcnt overflow.
From the CVE record · Linux
The Linux kernel’s SCTP stream priority cleanup can enter a large nested loop when freeing a stream’s priority, potentially causing a CPU soft lockup. The input does not specify how an attacker could trigger this behavior or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with SCTP support should check their versions; affected versions are not specified in the input.