CVE-2023-53590 Details
Description
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.
A vulnerability in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation can lead to a performance issue. The vulnerability arises because the priority management for SCTP streams does not properly account for how many streams are using a given priority. This oversight can cause a nested loop when freeing stream priorities, potentially leading to a 'soft lockup' where a CPU gets stuck for an extended period. The issue has been addressed by adding a reference count to the stream priorities, allowing the system to manage priorities more efficiently and avoid the performance bottleneck.
Users can upgrade to the patched version of the Linux kernel where this vulnerability has been addressed. The specific commit containing the fix can be found in the Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/03c3a5584a0a29821e59b7834635ce823050caaa | kernel.org | Patch |
| https://git.kernel.org/stable/c/68ba44639537de6f91fe32783766322d41848127 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6d529928ea212127851a2df8c40d822237ca946b | kernel.org | Patch |
| https://git.kernel.org/stable/c/8ee401f89cdb10f39098c0656d695b2bc4052100 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bf5540cbd20e2dae2c81ab9b31deef41ef147d0a | kernel.org | Patch |
| https://git.kernel.org/stable/c/cec326443f01283ef68ea00c06ea073b1835a562 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.4.226, < 5.4.235 >= 5.10.158, < 5.10.173 >= 5.15.82, < 5.15.100 >= 6.0.12, < 6.1 >= 6.1.1, < 6.1.18 >= 6.2, < 6.2.5 6.1 - 6.1 rc8 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 21, 2026 | Modified Analysis | [email protected] |
| Feb 9, 2026 | Initial Analysis | [email protected] |
| Oct 4, 2025 | New CVE Received | kernel.org |