UBUNTU-CVE-2026-93116: High severity ubuntu/linux-hwe-edge vulnerability
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
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In the asus-wmi driver's asus_wmi_add() error path, reorder the labels to exactly match the reverse order of resource allocations, including ensuring failures from asus_screenpad_init() jump through fail_screenpad and failures from asus_wmi_custom_fan_curve_init() jump through fail_custom_fan_curve, so cleanup for backlight, rfkill, the input device, and sysfs groups is executed without resource leaks.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue is in the ASUS WMI platform driver during initialization, so exposure is limited to systems where that driver is used. The affected Ubuntu kernel package lines listed are linux-riscv, linux-realtime, linux-azure, linux-gcp, linux-azure-fde, linux-gke, linux-hwe-edge, and linux-gkeop.
What conditions are needed to trigger the resource leaks?
A failure must occur during asus_wmi_add() after earlier subsystems have registered successfully. The affected failure cases are failures in custom fan-curve initialization or ScreenPad initialization.
What is the impact if the issue is triggered?
The driver can leave previously registered resources unreleased after probe failure. The leaked resources can include input-device and sysfs registrations, or backlight and rfkill resources, depending on where initialization fails.
What does the available fix change?
The fix reorders the asus_wmi_add() error-path labels so cleanup runs in the exact reverse order of resource allocation. This ensures resources registered before a later initialization failure are released.