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.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
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.
Sources
Also known as DEBIAN-CVE-2026-93124, GHSA-jvjx-cfgv-jw7v, UBUNTU-CVE-2026-93124.