# CVE-2026-90329: HID: synchronize input before cleaning up a failed probe

> A use-after-free in the Linux kernel HID subsystem allows attackers to execute arbitrary code or escalate privileges via race conditions during failed device probes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** AZL-101969, BELL-CVE-2026-90329, DEBIAN-CVE-2026-90329, GHSA-94w3-hvfp-6j85, UBUNTU-CVE-2026-90329

## What is CVE-2026-90329?

CVE-2026-90329 is a high-severity 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: synchronize input before cleaning up a failed probe

hid_device_io_start() allows reports to run concurrently with probe. If
the probe subsequently fails, __hid_device_probe() releases driver
resources and clears hdev->driver without first excluding those report
callbacks.

For example, a report may enter hidraw_report_event() while the failure
path frees the associated hidraw object, leading to a use-after-free when
the report takes the object's list lock.

Stop input before performing failed-probe cleanup. This reacquires
driver_input_lock and waits for any report callback already in progress.

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


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

Apply the vendor's patch.

## Is CVE-2026-90329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90329 is a high-severity 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-90329 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-90329/ (Markdown: https://insights.sbomify.com/CVE-2026-90329/index.md)
```

## Sources

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

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