{"id":"CVE-2026-93116","state":"PUBLISHED","title":"platform/x86: asus-wmi: fix resource leaks on probe failure","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wmi: fix resource leaks on probe failure\n\nDuring driver initialization in asus_wmi_add(), various subsystems are\nregistered sequentially. However, the error path labels are out of order\nrelative to the registration sequence.\n\nSpecifically:\n1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to\n   fail_custom_fan_curve. Because this label is placed below fail_sysfs,\n   it bypasses the cleanup calls for the input device and sysfs groups,\n   which were successfully registered before, leaking those resources.\n2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad.\n   Because fail_screenpad is placed below fail_backlight, it bypasses the\n   cleanup calls for backlight and rfkill, leaking those resources.\n\nFix these resource leaks by reordering the error path labels in\nasus_wmi_add() to match the exact reverse order of the resource\nallocations.","publishedAt":"2026-09-17T16:11:23.852Z","updatedAt":"2026-10-30T12:36:01.447Z","severity":{"score":7,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"72d792c8053f238ae541fdaa90e609548509b65f","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"959ed35f8c8f07b8dd43c3f917a43ae2f77e4471","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"8d5999608da60db45949e5459f74f581cdaacd04","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"8410cd2690d463b60527d00ac8cffea2d5a041f6","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"3308b8c5f5a28403611a2f5a46f06aabe4f0c661","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/platform/x86/asus-wmi.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.17","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.17","versionType":"semver"},{"version":"6.1.191","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.6.160","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.12.114","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.18.57","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.2.6","status":"unaffected","lessThanOrEqual":"7.2.*","versionType":"semver"},{"version":"7.3","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/platform/x86/asus-wmi.c"]}],"references":["https://git.kernel.org/stable/c/72d792c8053f238ae541fdaa90e609548509b65f","https://git.kernel.org/stable/c/959ed35f8c8f07b8dd43c3f917a43ae2f77e4471","https://git.kernel.org/stable/c/8d5999608da60db45949e5459f74f581cdaacd04","https://git.kernel.org/stable/c/8410cd2690d463b60527d00ac8cffea2d5a041f6","https://git.kernel.org/stable/c/3308b8c5f5a28403611a2f5a46f06aabe4f0c661","https://git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"],"weaknesses":[],"ingestedAt":"2026-10-30T12:54:04.478Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/93xxx/CVE-2026-93116.json","commit":"1f312381e38164a43607eebab851b151dd16861e","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-93116","state":"PUBLISHED","datePublished":"2026-09-17T16:11:23.852Z","dateUpdated":"2026-10-30T12:36:01.447Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2026-09-17T16:02:15.086Z"},"containers":{"cna":{"title":"platform/x86: asus-wmi: fix resource leaks on probe failure","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: asus-wmi: fix resource leaks on probe failure\n\nDuring driver initialization in asus_wmi_add(), various subsystems are\nregistered sequentially. However, the error path labels are out of order\nrelative to the registration sequence.\n\nSpecifically:\n1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to\n   fail_custom_fan_curve. Because this label is placed below fail_sysfs,\n   it bypasses the cleanup calls for the input device and sysfs groups,\n   which were successfully registered before, leaking those resources.\n2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad.\n   Because fail_screenpad is placed below fail_backlight, it bypasses the\n   cleanup calls for backlight and rfkill, leaking those resources.\n\nFix these resource leaks by reordering the error path labels in\nasus_wmi_add() to match the exact reverse order of the resource\nallocations."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"72d792c8053f238ae541fdaa90e609548509b65f","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"959ed35f8c8f07b8dd43c3f917a43ae2f77e4471","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"8d5999608da60db45949e5459f74f581cdaacd04","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"8410cd2690d463b60527d00ac8cffea2d5a041f6","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"3308b8c5f5a28403611a2f5a46f06aabe4f0c661","versionType":"git"},{"version":"0f0ac158d28ff78e75c334e869b1cb8e69372a1f","status":"affected","lessThan":"ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/platform/x86/asus-wmi.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.17","status":"affected"},{"version":"0","status":"unaffected","lessThan":"5.17","versionType":"semver"},{"version":"6.1.191","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.6.160","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.12.114","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.18.57","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.2.6","status":"unaffected","lessThanOrEqual":"7.2.*","versionType":"semver"},{"version":"7.3","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/platform/x86/asus-wmi.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/72d792c8053f238ae541fdaa90e609548509b65f"},{"url":"https://git.kernel.org/stable/c/959ed35f8c8f07b8dd43c3f917a43ae2f77e4471"},{"url":"https://git.kernel.org/stable/c/8d5999608da60db45949e5459f74f581cdaacd04"},{"url":"https://git.kernel.org/stable/c/8410cd2690d463b60527d00ac8cffea2d5a041f6"},{"url":"https://git.kernel.org/stable/c/3308b8c5f5a28403611a2f5a46f06aabe4f0c661"},{"url":"https://git.kernel.org/stable/c/ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The leak is created in asus_wmi_add() called from asus_wmi_probe() during asus_wmi_register_driver()'s platform_create_bundle() for asus-nb-wmi/eeepc-wmi module init; leftover rfkill objects are later driven via /dev/rfkill (rfkill_fop_write), not by a network or radio protocol message.\nAC:H - The dangling asus_rfkill exists only when asus_screenpad_init() returns an error other than -ENODEV after asus_wmi_rfkill_init() has registered devices, which requires an ACPI WMI failure from asus_wmi_get_devstate()/asus_wmi_evaluate_method() or backlight_device_register() failure that the attacker cannot induce.\nPR:L - After fail_screenpad skips asus_wmi_rfkill_exit(), the leaked rfkill stays on rfkill_list; rfkill_fop_write() has no capable() check, so a local session user who can open /dev/rfkill (typical laptop rfkill group/uaccess) can send RFKILL_OP_CHANGE and reach asus_rfkill_set() without CAP_SYS_ADMIN.\nUI:N - The attacker themselves writes RFKILL_OP_CHANGE/CHANGE_ALL to /dev/rfkill targeting the leaked asus-wlan/asus-bluetooth rfkill idx; no other user must mount media, plug a device, or confirm a prompt.\nS:U - kfree(asus) on the asus_wmi_add() fail_screenpad path and the later asus_rfkill_query()/asus_rfkill_set() dereference of priv->asus occur in the host kernel; this is not a KVM/Xen guest escape or IOMMU/DMA bypass.\nC:H - fail_screenpad jumps past asus_wmi_rfkill_exit() and then kfree(asus) while rfkill->data still points at the embedded struct asus_rfkill; rfkill_set_block() calls asus_rfkill_query(), which reads priv->asus and priv->dev_id from that freed object, a kernel UAF read.\nI:H - The same dangling rfkill->data is passed to asus_rfkill_set()/asus_rfkill_wlan_set(), which use priv->asus->driver and mutex_lock(&asus->wmi_lock); the leaked backlight_device also keeps bl_get_data()==asus for update_bl_status(), so reclaiming the freed asus_wmi object is a write/control-flow primitive.\nA:H - asus_rfkill_query() and asus_rfkill_set() dereference the kfree'd struct asus_wmi, and asus_rfkill_wlan_set() takes asus->wmi_lock in freed memory, which oopses; fail_custom_fan_curve also skips asus_wmi_input_exit(), leaving a registered input_dev until reboot."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-10-30T12:36:01.447Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.1.191"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.6.160"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.12.114"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.18.57"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"7.2.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"7.3"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}}}}}