HID: asus: refactor the two workqueues and init sequence
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1489a34e97efebf583ff08e506ecf9f7d44537d3 · fixed in 744b3f930c1173ad57f49b614fc875d8d2715396; From 1489a34e97efebf583ff08e506ecf9f7d44537d3 · fixed in 47669bec44fe12fe2c7adf2b299e980d7935a2ce
- Linux Linux
7.0
- KernelLinux
From 7.0.0 · fixed in 7.2.6