# CVE-2026-74437: media: uvcvideo: Fix deadlock if uvc_status_stop is called from async_ctrl.work

> A deadlock in the Linux kernel's uvcvideo driver can cause a denial of service when a UVC camera triggers specific asynchronous control events.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74437, DEBIAN-CVE-2026-74437, GHSA-5vf9-4h4x-m5f6, UBUNTU-CVE-2026-74437

## What is CVE-2026-74437?

CVE-2026-74437 is a vulnerability in Linux, published on 15 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: uvcvideo: Fix deadlock if uvc_status_stop is called from async_ctrl.work

If a UVC camera has an asynchronous control, uvc_status_stop may be
called from async_ctrl.work:

uvc_ctrl_status_event_work()
    uvc_ctrl_status_event()
        uvc_ctrl_clear_handle()
	    uvc_pm_put()
	        uvc_status_put()
		    uvc_status_stop()
		        cancel_work_sync()

This will cause a deadlock, since cancel_work_sync will wait for
uvc_ctrl_status_event_work to complete before returning.

Fix this by returning early from uvc_status_stop if we are currently in
the work function. flush_status now remains false until uvc_status_start
is called again, ensuring that uvc_ctrl_status_event_work won't resubmit
the URB.

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


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

Apply the vendor's patch.

## Is CVE-2026-74437 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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