ghsa-h343-797x-8cg9
Vulnerability from github
Published
2025-10-04 18:31
Modified
2025-10-04 18:31
Details

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.

Show details on source website

To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-53590"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-04T16:15:55Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: add a refcnt in sctp_stream_priorities to avoid a nested loop\n\nWith this refcnt added in sctp_stream_priorities, we don\u0027t need to\ntraverse all streams to check if the prio is used by other streams\nwhen freeing one stream\u0027s prio in sctp_sched_prio_free_sid(). This\ncan avoid a nested loop (up to 65535 * 65535), which may cause a\nstuck as Ying reported:\n\n    watchdog: BUG: soft lockup - CPU#23 stuck for 26s! [ksoftirqd/23:136]\n    Call Trace:\n     \u003cTASK\u003e\n     sctp_sched_prio_free_sid+0xab/0x100 [sctp]\n     sctp_stream_free_ext+0x64/0xa0 [sctp]\n     sctp_stream_free+0x31/0x50 [sctp]\n     sctp_association_free+0xa5/0x200 [sctp]\n\nNote that it doesn\u0027t need to use refcount_t type for this counter,\nas its accessing is always protected under the sock lock.\n\nv1-\u003ev2:\n - add a check in sctp_sched_prio_set to avoid the possible prio_head\n   refcnt overflow.",
  "id": "GHSA-h343-797x-8cg9",
  "modified": "2025-10-04T18:31:15Z",
  "published": "2025-10-04T18:31:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53590"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/03c3a5584a0a29821e59b7834635ce823050caaa"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/68ba44639537de6f91fe32783766322d41848127"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6d529928ea212127851a2df8c40d822237ca946b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8ee401f89cdb10f39098c0656d695b2bc4052100"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bf5540cbd20e2dae2c81ab9b31deef41ef147d0a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cec326443f01283ef68ea00c06ea073b1835a562"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.