# CVE-2026-90022: usb: gadget: f_midi2: fix use-after-free in string attribute show path

> A race condition in the Linux kernel USB MIDI gadget driver allows a local attacker to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101373, BELL-CVE-2026-90022, DEBIAN-CVE-2026-90022, GHSA-3v5g-8x87-gm3v, UBUNTU-CVE-2026-90022

## What is CVE-2026-90022?

CVE-2026-90022 is a high-severity use after free vulnerability in Linux, published on 16 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:

usb: gadget: f_midi2: fix use-after-free in string attribute show path

f_midi2_opts_str_show() takes the string lock internally, but its
callers dereference the opts->info.<field> pointer before calling it,
outside the lock. This races with f_midi2_opts_str_store(), which
frees the old string under opts->lock when the attribute is written
concurrently, the show path can read a pointer that gets freed
before the lock inside str_show() is even taken.

Change f_midi2_opts_str_show() to take a pointer to the string field,
matching the existing pattern in f_midi2_opts_str_store(), and
dereference it only after the lock is held. Update all three callers
(iface_name, block name, and the EP string option macro) accordingly.

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


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

Apply the vendor's patch.

## Is CVE-2026-90022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90022 is a high-severity use after free vulnerability in Linux, published on 16 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-90022 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-90022/ (Markdown: https://insights.sbomify.com/CVE-2026-90022/index.md)
```

## Sources

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

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