CVE-2026-93184: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-93184 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-2026-93184 at a Glance
How to Fix CVE-2026-93184
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-2026-93184, 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-2026-93184?
Which Software versions are affected?
What version fixes CVE-2026-93184?
What CWE is associated with CVE-2026-93184?
How can I check Maven dependencies for CVE-2026-93184?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-88wf-2wr7-wjcj",
"modified" : "2026-09-17T18:32:13Z",
"published" : "2026-09-17T18:32:13Z",
"aliases" : [ "CVE-2026-93184" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: fsl_audmix: rework runtime PM handling in probe\n\nAfter pm_runtime_enable() the AUDMIX block is powered off and stays\nsuspended until the first runtime resume. Register writes issued between\nprobe() and the first resume (e.g. from DAPM or ALSA control paths)\ntarget unpowered hardware and cause a system hang.\n\nFix this by calling pm_runtime_resume_and_get() immediately after\npm_runtime_enable() to power the hardware up and enable its clocks.\nRelease the reference afterwards with pm_runtime_put() to allow the\nruntime PM framework to suspend the device and switch the regmap to\ncache-only mode when idle.\n\nWhen CONFIG_PM is disabled or runtime PM is not enabled, pm_runtime_*\ncalls are stubs that do not power up the hardware. Handle this case\nexplicitly by calling fsl_audmix_runtime_resume() directly so the\nhardware is always initialised and its clocks are enabled, ensuring\nregister accesses succeed regardless of PM configuration.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93184"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/22c944e440bc9b16c4ee409943d69bb8ef575c9e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3359ba93d01a23b2e4249e9e44ccfe48eb9c5d71"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b5c3f8015af442c2411722cf8c220cfbae271230"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e921cc73fae68ccee932ad0a4fb11d637557db0e"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:18:14Z"
}
}