# CVE-2026-89877: media: saa7164: fix cleanup on resource allocation failure

> A use-after-free vulnerability in the saa7164 media driver allows attackers to cause denial of service or execute code via improper cleanup on resource allocation failure.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101640, BELL-CVE-2026-89877, DEBIAN-CVE-2026-89877, GHSA-33q9-xpr9-fmxv, UBUNTU-CVE-2026-89877

## What is CVE-2026-89877?

CVE-2026-89877 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: saa7164: fix cleanup on resource allocation failure

saa7164_dev_setup() adds the device to the global saa7164_devlist before
requesting the PCI BAR memory regions.

If get_resources() fails, saa7164_dev_setup() decrements the device count
and returns an error, but leaves the device on saa7164_devlist. The probe
error path then frees the device, leaving a dangling entry on the global
list.

Reuse the existing MMIO mapping error path to remove the device from
saa7164_devlist and decrement the device count before returning.

Also release BAR0 if it was successfully requested but the BAR2 request
fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-89877 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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