# CVE-2026-74642: ALSA: usb: Fix UAF at delayed release of MIDI2 EPs

> A use-after-free vulnerability in the Linux kernel's ALSA USB MIDI2 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:** 22 Aug 2026
- **Updated:** 22 Aug 2026
- **Also known as:** BELL-CVE-2026-74642, DEBIAN-CVE-2026-74642, GHSA-r4jc-x475-grgg, UBUNTU-CVE-2026-74642

## What is CVE-2026-74642?

CVE-2026-74642 is an use after free vulnerability in Linux, published on 22 Aug 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:

ALSA: usb: Fix UAF at delayed release of MIDI2 EPs

The recent fix for UAF in ump_to_endpoint() caused another UAF because
it tries to dereference the UMP endpoint object, but this might be
executed at a delayed context where the endpoint has been already
released.

Add private_free to clear the associated data for avoiding the further
dereference for delayed releases.

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


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

Apply the vendor's patch.

## Is CVE-2026-74642 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74642 is an use after free vulnerability in Linux, published on 22 Aug 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-74642 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-74642/ (Markdown: https://insights.sbomify.com/CVE-2026-74642/index.md)
```

## Sources

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

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