# CVE-2026-98316: ALSA: bcd2000: Fix race between rawmidi and disconnect

> A race condition in the ALSA bcd2000 driver allows local attackers to trigger a use-after-free during USB disconnect, potentially causing system crashes 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:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106470, BELL-CVE-2026-98316, DEBIAN-CVE-2026-98316, GHSA-877f-c8m6-hq9r, UBUNTU-CVE-2026-98316

## What is CVE-2026-98316?

CVE-2026-98316 is a vulnerability in Linux, published on 6 Oct 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: bcd2000: Fix race between rawmidi and disconnect

Although we tried to fix the potential UAF issues at USB disconnect on
bcd2000 driver, there is still an overlooked case -- namely, when a
rawmidi trigger callback has been already running at USB disconnect
handling, the in-flight function (e.g. bcd2000_midi_send()) could
still access the URB, because the previous URB NULL-check & clearance
was considered only for the URB complete callbacks, but not about the
parallel rawmidi operations.

For addressing the race, this patch introduced a new spinlock that
covers each rawmidi operation as well as the rawmidi handling in the
complete callback.  The URB is cleared with the lock, so it guarantees
that the pending rawmidi task already finished or a NULL check is
effective.

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


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

Apply the vendor's patch.

## Is CVE-2026-98316 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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