# CVE-2026-90331: HID: asus: refactor the two workqueues and init sequence

> A use-after-free vulnerability in the Linux kernel HID ASUS driver allows local attackers to execute arbitrary code or escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90331, GHSA-crc6-vh29-6g24, UBUNTU-CVE-2026-90331

## What is CVE-2026-90331?

CVE-2026-90331 is an use after free 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:

HID: asus: refactor the two workqueues and init sequence

Multiple issues have been found within the hid-asus driver:
- unchecked size in asus_raw_event()
- unclean teardown of asus_probe on failure
- possible use-after-free in asus_probe
- multiple workqueue used for jobs where one was enough
- sleeping calls in atomic context
- packets of incorrect size being sent to the keyboard controller

Join the two workqueues into one reusing the stopping mechanism
of the brightness workqueue, use the joined workqueue to also
move the asus_wmi_send_event() sleeping call away from atomic
context and add a size check in asus_raw_event().

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


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

Apply the vendor's patch.

## Is CVE-2026-90331 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90331 is an use after free 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-90331 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-90331/ (Markdown: https://insights.sbomify.com/CVE-2026-90331/index.md)
```

## Sources

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

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