# CVE-2026-93101: media: v4l2-async: Unregister sub-device if asc_list is empty

> A null pointer dereference in the Linux kernel media subsystem causes a system crash when specific USB video devices are disconnected.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102942, BELL-CVE-2026-93101, DEBIAN-CVE-2026-93101, GHSA-3xmx-x378-q7fc, UBUNTU-CVE-2026-93101

## What is CVE-2026-93101?

CVE-2026-93101 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

media: v4l2-async: Unregister sub-device if asc_list is empty

When my em28xx USB device that uses the i2c tvp5150 driver is
disconnected, it crashes.

The cause is that the tvp5150 i2c module uses v4l2_async, but
the em28xx driver does not since it predates v4l2_async.

In that corner case sd->asc_list is empty, so
v4l2_async_unregister_subdev() never calls v4l2_device_unregister_subdev().

Modify the code so that, if sd->asc_list is empty,
v4l2_device_unregister_subdev() is still called.

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


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

Apply the vendor's patch.

## Is CVE-2026-93101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93101 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93101 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-93101/ (Markdown: https://insights.sbomify.com/CVE-2026-93101/index.md)
```

## Sources

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

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