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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-21 12:51
- References+2 references (now 5)NVD modified 2026-10-21 13:20
- StatusPublished → ReceivedNVD modified 2026-10-21 13:20
- StatusReceived → PublishedNVD modified 2026-10-19 09:05
- First seenCVSS 7.0NVD modified 2026-10-15 11:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/3308b8c5f5a28403611a2f5a46f06aabe4f0c661
- https://git.kernel.org/stable/c/8410cd2690d463b60527d00ac8cffea2d5a041f6
- https://git.kernel.org/stable/c/8d5999608da60db45949e5459f74f581cdaacd04
- https://git.kernel.org/stable/c/959ed35f8c8f07b8dd43c3f917a43ae2f77e4471
- https://git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95