Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53590sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53590, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a7555681e50bdebed2c40ff7404ee73c2e932993 – < cec326443f01283ef68ea00c06ea073b1835a562
    • affected 176ee6c673ccd118e9392fd2dbb165423bdb99ca – < 8ee401f89cdb10f39098c0656d695b2bc4052100
    • affected 0dfb9a566327182387c90100ea54d8426cee8c67 – < bf5540cbd20e2dae2c81ab9b31deef41ef147d0a
    • affected 9ed7bfc79542119ac0a9e1ce8a2a5285e43433e9 – < 03c3a5584a0a29821e59b7834635ce823050caaa
    • affected 9ed7bfc79542119ac0a9e1ce8a2a5285e43433e9 – < 6d529928ea212127851a2df8c40d822237ca946b
    • affected 9ed7bfc79542119ac0a9e1ce8a2a5285e43433e9 – < 68ba44639537de6f91fe32783766322d41848127
    • affected fa20f88271259d42ebe66f0a8c4c20199e888c99
    • affected 5.4.226 – < 5.4.235
    • affected 5.10.158 – < 5.10.173
    • affected 5.15.82 – < 5.15.100
    • affected 6.0.12 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.100 – ≤ 5.15.*
    • unaffected 6.1.18 – ≤ 6.1.*
    • unaffected 6.2.5 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53590 badge
[![CVE-2023-53590](https://cveledger.app/badge/CVE-2023-53590.svg)](https://cveledger.app/cve/CVE-2023-53590)

Record last updated .