platform/x86: asus-wireless: Fail probe when there is no ACPI match
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7 and Kernel 7bfa711f311a584002e16ecd750627306deb805c.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=f7e648027d7e1b5c06eb86d944b7e23926254cee <4aefd66ef7822cf7d3f53146dcee0b71021ed2b7, >=f7e648027d7e1b5c06eb86d944b7e23926254cee <7bfa711f311a584002e16ecd750627306deb805c | 4aefd66ef7822cf7d3f53146dcee0b71021ed2b7, 7bfa711f311a584002e16ecd750627306deb805c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket