# CVE-2026-93071: media: bcm2835-unicam: Fix asc leaked in error/remove path

> A memory leak in the BCM2835 Unicam driver allows local attackers to exhaust kernel memory, potentially causing a denial of service.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93071, DEBIAN-CVE-2026-93071, GHSA-m33f-v49h-44x7, UBUNTU-CVE-2026-93071

## What is CVE-2026-93071?

CVE-2026-93071 is a memory corruption vulnerability in Linux, published on 17 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: bcm2835-unicam: Fix asc leaked in error/remove path

v4l2_async_nf_add_fwnode_remote() allocates the asc, which is freed when
v4l2_async_nf_cleanup() is called.

Call v4l2_async_nf_cleanup() properly in the driver paths.

Discovered with kmemleak after rmmod:

unreferenced object 0xffff000084526b80 (size 64):
  comm "modprobe", pid 185, jiffies 4295013512
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 e8 0d ff bf 00 00 ff ff  ................
    40 83 bc 84 00 00 ff ff 60 83 bc 84 00 00 ff ff  @.......`.......
  backtrace (crc ac584083):
    [<00000000ffb081a7>] kmemleak_alloc+0x38/0x44
    [<00000000d2fd9301>] __kmalloc+0x1b0/0x250
    [<000000004dd5354d>] __v4l2_async_nf_add_fwnode+0x28/0x9c
    [<0000000067587657>] __v4l2_async_nf_add_fwnode_remote+0x3c/0x64

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


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

Apply the vendor's patch.

## Is CVE-2026-93071 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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