# CVE-2026-90330: HID: logitech-hidpp: Fix FF device cleanup on init failure

> A memory leak in the Logitech HID++ driver allows local attackers to cause denial of service via resource exhaustion during device initialization failures.

- **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:** 21 Oct 2026
- **Also known as:** AZL-102267, BELL-CVE-2026-90330, DEBIAN-CVE-2026-90330, GHSA-659p-736p-fqhx, UBUNTU-CVE-2026-90330

## What is CVE-2026-90330?

CVE-2026-90330 is a memory corruption 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: logitech-hidpp: Fix FF device cleanup on init failure

hidpp_ff_init() creates the input force-feedback device with
input_ff_create(), then allocates the HID++ FF private data,
effect ID array, and workqueue.

If any of those allocations fail after input_ff_create() succeeds,
the function returns an error without destroying the FF device.
Add an unwind path that frees the private allocations made by
hidpp_ff_init() and calls input_ff_destroy() for failures after
input_ff_create() succeeds.

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


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

Apply the vendor's patch.

## Is CVE-2026-90330 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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