# CVE-2026-80650: media: atomisp: gc2235: fix UAF and memory leak

> A use-after-free vulnerability in the Linux kernel gc2235 camera driver allows local attackers to execute arbitrary code or cause a system crash.

- **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:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-98124, BELL-CVE-2026-80650, DEBIAN-CVE-2026-80650, GHSA-g5xp-8jpc-79mv, UBUNTU-CVE-2026-80650

## What is CVE-2026-80650?

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

media: atomisp: gc2235: fix UAF and memory leak

gc2235_probe() handles its error paths incorrectly.

If media_entity_pads_init() fails, gc2235_remove() is called, which
tears down the subdev and frees dev, but then still falls through to
atomisp_register_i2c_module(). This results in use-after-free.

If atomisp_register_i2c_module() fails, the media entity and control
handler are left initialized and dev is leaked.

gc2235_remove() unconditionally calls media_entity_cleanup() and
v4l2_ctrl_handler_free(), but these are not initialized at every
error path in gc2235_probe().

Replace gc2235_remove() calls in the probe error paths with explicit
unwind labels that free only the resources initialized at each point
of failure, in reverse order of initialization.

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


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

Apply the vendor's patch.

## Is CVE-2026-80650 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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