# CVE-2026-93116: platform/x86: asus-wmi: fix resource leaks on probe failure

> A resource leak in the ASUS WMI driver during probe failure can lead to memory exhaustion and denial of service.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102102, BELL-CVE-2026-93116, DEBIAN-CVE-2026-93116, GHSA-5872-jrxc-47c3, UBUNTU-CVE-2026-93116

## What is CVE-2026-93116?

CVE-2026-93116 is a high-severity denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93116?


## How do I fix CVE-2026-93116?

Apply the vendor's patch.

## Is CVE-2026-93116 being exploited?

There is no known exploitation of CVE-2026-93116 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93116 and fix it if it is affected.

What it is: CVE-2026-93116 is a high-severity denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93116 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93116/ (Markdown: https://insights.sbomify.com/CVE-2026-93116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93116
- OSV: https://osv.dev/vulnerability/CVE-2026-93116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93116/
Summaries are generated and may contain mistakes; the official description above is the record.