HID: asus: refactor the two workqueues and init sequence
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
HID: asus: refactor the two workqueues and init sequence
Multiple issues have been found within the hid-asus driver: - unchecked size in asus_raw_event() - unclean teardown of asus_probe on failure - possible use-after-free in asus_probe - multiple workqueue used for jobs where one was enough - sleeping calls in atomic context - packets of incorrect size being sent to the keyboard controller
Join the two workqueues into one reusing the stopping mechanism of the brightness workqueue, use the joined workqueue to also move the asus_wmi_send_event() sleeping call away from atomic context and add a size check in asus_raw_event().
From the CVE record · Linux
The Linux kernel's hid-asus driver has an unchecked event size, probe cleanup and possible use-after-free issues, and other workqueue and packet-handling problems. The input does not specify what an attacker could do or whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with the hid-asus driver should check their versions; affected versions are not specified.