CVE-2026-93116: platform/x86: asus-wmi: fix resource leaks on probe failure
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: asus-wmi: fix resource leaks on probe failure
During driver initialization in asuswmiadd(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence.
Specifically: 1. If asuswmicustomfancurveinit() fails, the driver jumps to failcustomfancurve. Because this label is placed below failsysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asusscreenpadinit() fails, the driver jumps to failscreenpad. Because failscreenpad is placed below failbacklight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources.
Fix these resource leaks by reordering the error path labels in asuswmiadd() to match the exact reverse order of the resource allocations.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.57 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1
Event History
Frequently Asked Questions
Is a system affected when the driver initializes successfully?
The described leaks occur only on specific initialization failure paths. The data does not indicate resource leaks during successful initialization.
Which initialization failures can trigger the leaked resources?
A failure in custom fan-curve initialization can leave the input device and sysfs groups uncleaned. A failure in ScreenPad initialization can leave backlight and rfkill resources uncleaned.