CVE-2023-53590: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-h343-797x-8cg9
Share
CVSS 5.5
CWE-667
Published
Advisory Summary

CVE-2023-53590 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-667: Improper Locking) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.. Remediation is available in the latest vendor maintenance releases.

CVE-2023-53590 at a Glance

CVE Identifier CVE-2023-53590
GHSA Identifier GHSA-h343-797x-8cg9
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-667: Improper Locking
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2023-53590

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2023-53590, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-667: Improper Locking, where the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2023-53590 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-53590
git.kernel.org/stable/c/03c3a5584a... WEB
https://git.kernel.org/stable/c/03c3a5584a0a29821e59b7834635ce823050caaa
git.kernel.org/stable/c/68ba446395... WEB
https://git.kernel.org/stable/c/68ba44639537de6f91fe32783766322d41848127
git.kernel.org/stable/c/6d529928ea... WEB
https://git.kernel.org/stable/c/6d529928ea212127851a2df8c40d822237ca946b
git.kernel.org/stable/c/8ee401f89c... WEB
https://git.kernel.org/stable/c/8ee401f89cdb10f39098c0656d695b2bc4052100
git.kernel.org/stable/c/bf5540cbd2... WEB
https://git.kernel.org/stable/c/bf5540cbd20e2dae2c81ab9b31deef41ef147d0a
git.kernel.org/stable/c/cec326443f... WEB
https://git.kernel.org/stable/c/cec326443f01283ef68ea00c06ea073b1835a562

Frequently Asked Questions

What is CVE-2023-53590?
CVE-2023-53590 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-667: Improper Locking.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2023-53590?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2023-53590?
CVE-2023-53590 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2023-53590?
CVE-2023-53590 is classified under CWE-667: Improper Locking (The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.).
How can I check Maven dependencies for CVE-2023-53590?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h343-797x-8cg9",
  "modified" : "2026-02-10T00:30:28Z",
  "published" : "2025-10-04T18:31:15Z",
  "aliases" : [ "CVE-2023-53590" ],
  "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't need to\ntraverse all streams to check if the prio is used by other streams\nwhen freeing one stream's 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     <TASK>\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't need to use refcount_t type for this counter,\nas its accessing is always protected under the sock lock.\n\nv1->v2:\n - add a check in sctp_sched_prio_set to avoid the possible prio_head\n   refcnt overflow.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "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"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-667" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-10-04T16:15:55Z"
  }
}