CVE-2026-93124: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-93124 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-93124 at a Glance
How to Fix CVE-2026-93124
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-93124, 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-93124?
Which Software versions are affected?
What version fixes CVE-2026-93124?
What CWE is associated with CVE-2026-93124?
How can I check Maven dependencies for CVE-2026-93124?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jvjx-cfgv-jw7v",
"modified" : "2026-09-17T18:32:11Z",
"published" : "2026-09-17T18:32:11Z",
"aliases" : [ "CVE-2026-93124" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wireless: Fail probe when there is no ACPI match\n\nEvery platform driver can be forced to match a device that does not match\nits list of device IDs because of device_match_driver_override(), so\nplatform drivers that rely on the existence of a device ACPI companion\nobject need to verify its presence.\n\nasus_wireless_probe() returns success when acpi_match_acpi_device()\nfinds no match, leaving behind an input device that never reports\nanything because the notify handler is not installed. Worse, when the\ndriver is force-bound to a device without an ACPI companion, probe\nstill succeeds and stores a NULL companion pointer, which\nasus_wireless_remove() later passes to acpi_dev_remove_notify_handler(),\nleading to a NULL pointer dereference on unbind.\n\nReturn -ENODEV when the device does not match the ID table. This also\ncovers the missing-companion case, because acpi_match_acpi_device()\nrejects a NULL device. Perform the check before allocating any driver\nstate, instead of after the input device has already been registered.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93124"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4aefd66ef7822cf7d3f53146dcee0b71021ed2b7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7bfa711f311a584002e16ecd750627306deb805c"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:18:07Z"
}
}