# CVE-2026-80594: Input: ims-pcu - fix potential infinite loop in CDC union descriptor parsing

> A malicious USB device can cause an infinite loop in the Linux kernel ims-pcu driver, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80594, DEBIAN-CVE-2026-80594, GHSA-3j49-838f-hr4g, UBUNTU-CVE-2026-80594

## What is CVE-2026-80594?

CVE-2026-80594 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Input: ims-pcu - fix potential infinite loop in CDC union descriptor parsing

The driver parses CDC union descriptors in ims_pcu_get_cdc_union_desc()
by iterating through the extra descriptor data. However, it does not
verify that the bLength of each descriptor is at least 2. A malicious
device could provide a descriptor with bLength = 0, leading to an
infinite loop in the driver.

Add a check to ensure bLength is at least 2 before proceeding with
parsing.

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


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

Apply the vendor's patch.

## Is CVE-2026-80594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80594 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-80594 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-80594/ (Markdown: https://insights.sbomify.com/CVE-2026-80594/index.md)
```

## Sources

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

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