# CVE-2026-89890: media: go7007: defer the ALSA v4l2 put until card release

> A use-after-free vulnerability in the Linux kernel go7007 driver allows local attackers to execute arbitrary code or escalate privileges via race conditions during device removal.

- **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-101684, BELL-CVE-2026-89890, DEBIAN-CVE-2026-89890, GHSA-qhgv-8fw2-7hch, UBUNTU-CVE-2026-89890

## What is CVE-2026-89890?

CVE-2026-89890 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:

media: go7007: defer the ALSA v4l2 put until card release

go7007_snd_init() already takes a v4l2_device reference for the ALSA
side, but go7007_snd_remove() drops it immediately after calling
snd_card_free_when_closed().

That is too early when a userspace process still has the capture PCM open.
The ALSA card and its PCM callbacks remain alive until the last file is
closed, so the release path can still reach struct go7007 through
pcm->private_data and call go7007_snd_hw_free() after the V4L2 release path
has freed the object.

Move the matching v4l2_device_put() to the ALSA card private_free callback
so the existing ALSA reference covers the whole deferred card lifetime.

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


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

Apply the vendor's patch.

## Is CVE-2026-89890 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89890 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-89890 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-89890/ (Markdown: https://insights.sbomify.com/CVE-2026-89890/index.md)
```

## Sources

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

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