# CVE-2026-72074: Input: ims-pcu - fix type confusion in CDC union descriptor parsing

> A type confusion flaw in the Linux kernel's ims-pcu driver allows local attackers to overwrite interface data, potentially leading to privilege escalation or code execution.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72074, DEBIAN-CVE-2026-72074, GHSA-cgj5-87r8-p5m2, UBUNTU-CVE-2026-72074

## What is CVE-2026-72074?

CVE-2026-72074 is a memory corruption vulnerability in Linux, published on 15 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 type confusion in CDC union descriptor parsing

The driver currently trusts the bMasterInterface0 from the CDC union
descriptor without verifying that it matches the interface being
probed. This could lead to the driver overwriting the private data of
another interface.

Validate that the control interface found in the descriptor is indeed
the one we are probing.

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


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

Apply the vendor's patch.

## Is CVE-2026-72074 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72074 is a memory corruption vulnerability in Linux, published on 15 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-72074 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-72074/ (Markdown: https://insights.sbomify.com/CVE-2026-72074/index.md)
```

## Sources

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

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