CVE-2023-54217: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2023-54217 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2023-54217 at a Glance
How to Fix CVE-2023-54217
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.
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-54217, 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 General Security Weakness. 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
References
Frequently Asked Questions
What is CVE-2023-54217?
Which Software versions are affected?
What version fixes CVE-2023-54217?
What CWE is associated with CVE-2023-54217?
How can I check Maven dependencies for CVE-2023-54217?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gj73-539r-gfvc",
"modified" : "2025-12-30T15:30:31Z",
"published" : "2025-12-30T15:30:31Z",
"aliases" : [ "CVE-2023-54217" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"drm/msm: Add missing check and destroy for alloc_ordered_workqueue\"\n\nThis reverts commit 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0.\n\nA recent patch that tried to fix up the msm_drm_init() paths with\nrespect to the workqueue but only ended up making things worse:\n\nFirst, the newly added calls to msm_drm_uninit() on early errors would\ntrigger NULL-pointer dereferences, for example, as the kms pointer would\nnot have been initialised. (Note that these paths were also modified by\na second broken error handling patch which in effect cancelled out this\npart when merged.)\n\nSecond, the newly added allocation sanity check would still leak the\npreviously allocated drm device.\n\nInstead of trying to salvage what was badly broken (and clearly not\ntested), let's revert the bad commit so that clean and backportable\nfixes can be added in its place.\n\nPatchwork: https://patchwork.freedesktop.org/patch/525107/",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-54217"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9078b434587722a6f2958dc1d536af6e39634db9"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2025-12-30T13:16:09Z"
}
}