# CVE-2026-93124: platform/x86: asus-wireless: Fail probe when there is no ACPI match

> A local attacker with high privileges can trigger a kernel crash by force-binding the asus-wireless driver to a device without an ACPI companion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93124, GHSA-jvjx-cfgv-jw7v, UBUNTU-CVE-2026-93124

## What is CVE-2026-93124?

CVE-2026-93124 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: asus-wireless: Fail probe when there is no ACPI match

Every platform driver can be forced to match a device that does not match
its list of device IDs because of device_match_driver_override(), so
platform drivers that rely on the existence of a device ACPI companion
object need to verify its presence.

asus_wireless_probe() returns success when acpi_match_acpi_device()
finds no match, leaving behind an input device that never reports
anything because the notify handler is not installed.  Worse, when the
driver is force-bound to a device without an ACPI companion, probe
still succeeds and stores a NULL companion pointer, which
asus_wireless_remove() later passes to acpi_dev_remove_notify_handler(),
leading to a NULL pointer dereference on unbind.

Return -ENODEV when the device does not match the ID table.  This also
covers the missing-companion case, because acpi_match_acpi_device()
rejects a NULL device.  Perform the check before allocating any driver
state, instead of after the input device has already been registered.

## Which versions are affected by CVE-2026-93124?


## How do I fix CVE-2026-93124?

Apply the vendor's patch.

## Is CVE-2026-93124 being exploited?

There is no known exploitation of CVE-2026-93124 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93124 and fix it if it is affected.

What it is: CVE-2026-93124 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93124 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93124/ (Markdown: https://insights.sbomify.com/CVE-2026-93124/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93124
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93124
- OSV: https://osv.dev/vulnerability/CVE-2026-93124

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93124/
Summaries are generated and may contain mistakes; the official description above is the record.