platform/x86: asus-wmi: fix resource leaks on probe failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0f0ac158d28ff78e75c334e869b1cb8e69372a1f · < ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: asus-wmi: fix resource leaks on probe failure
During driver initialization in asus_wmi_add(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence.
Specifically: 1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to fail_custom_fan_curve. Because this label is placed below fail_sysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad. Because fail_screenpad is placed below fail_backlight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources.
Fix these resource leaks by reordering the error path labels in asus_wmi_add() to match the exact reverse order of the resource allocations.
From the CVE record · Linux
The Linux kernel's asus-wmi driver can leak registered resources if custom fan curve or ScreenPad initialization fails during device probing. The input does not describe an attacker-controlled trigger, authentication requirements, or user interaction.
Engineers running Linux systems that use the asus-wmi driver should check their kernel; affected versions are not specified.