CVE-2026-99518
platform/x86: asus-wmi: fix use-after-free unregistering kbd_led led
Description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: asus-wmi: fix use-after-free unregistering kbd_led led kbd_led_update_all() registers asus->kbd_led with devm_led_classdev_register() on the platform device, but kbd_led is embedded in struct asus_wmi, which asus_wmi_remove() frees at its end. The driver core calls .remove() before devres_release_all(), so the deferred devres release runs led_classdev_unregister() on memory that has already been freed. Whether that faults depends on whether the slab has been reused in between, which makes the crash on module unload intermittent and silently corrupts the led classdev state in the remaining runs. Unregister the led classdev explicitly in asus_wmi_led_exit(), after the led workqueue has been destroyed: kbd_led_work can then neither run nor be queued anymore, since asus_ref.asus is NULL too, so kbd_led_registered is stable and the classdev can be released while the memory embedding it is still alive. devm_led_classdev_unregister() also drops the devres entry, leaving nothing to run at unbind cleanup time; it warns when no devres entry exists, hence the kbd_led_registered check.
INFO
Published Date :
Nov. 19, 2026, 2:44 p.m.
Last Modified :
Nov. 19, 2026, 2:44 p.m.
Remotely Exploit :
No
Source :
Linux
Solution
- Unregister led classdev explicitly in asus_wmi_led_exit().
- Destroy the led workqueue before unregistering.
- Ensure kbd_led_registered is stable.
- Use devm_led_classdev_unregister() to drop devres entry.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-99518 vulnerability anywhere in the article.