CVE-2023-53590

sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop

MEDIUM
5.5
CVSS Score
Published: October 4, 2025 at 03:44 PM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.0.125.10.158 ≤ v < 5.10.1735.15.82 ≤ v < 5.15.1005.4.226 ≤ v < 5.4.2356.0.12 ≤ v < 6.16.1 ≤ v < 6.1.186.1 ≤ v < 6.2.56.1 ≤ v < 6.36.1.1 ≤ v < 6.1.186.2 ≤ v < 6.2.50dfb9a566327182387c90100ea54d8426cee8c67176ee6c673ccd118e9392fd2dbb165423bdb99ca5.10.1585.15.825.4.2266.0.126.16.1 rc89ed7bfc79542119ac0a9e1ce8a2a5285e43433e9a7555681e50bdebed2c40ff7404ee73c2e932993fa20f88271259d42ebe66f0a8c4c20199e888c99
Vendor states this is fixed in 03c3a5584a0a29821e59b7834635ce823050caaa (fixed)
Vendor states this is fixed in 68ba44639537de6f91fe32783766322d41848127 (fixed)
Vendor states this is fixed in 6d529928ea212127851a2df8c40d822237ca946b (fixed)
Vendor states this is fixed in 8ee401f89cdb10f39098c0656d695b2bc4052100 (fixed)
Vendor states this is fixed in bf5540cbd20e2dae2c81ab9b31deef41ef147d0a (fixed)
Vendor states this is fixed in cec326443f01283ef68ea00c06ea073b1835a562 (fixed)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.100 (unaffected)
Vendor states this is fixed in 5.4.235 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.18 (unaffected)
Vendor states this is fixed in 6.2.5 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card