# CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path

> A race condition in the Linux kernel VDUSE driver allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74313, DEBIAN-CVE-2026-74313, GHSA-m274-mg38-f4wj, UBUNTU-CVE-2026-74313

## What is CVE-2026-74313?

CVE-2026-74313 is a high-severity use after free 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:

vduse: hold vduse_lock across IDR lookup in open path

vduse_dev_open() looks up struct vduse_dev through the IDR and then
acquires dev->lock only after vduse_lock has been dropped.

This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the
same object from the IDR and free it before the open path locks the
device, leading to a use-after-free.

Close this race by keeping vduse_lock held until dev->lock has been
acquired in the open path, matching the lock ordering already used by
the destroy path.

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


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

Apply the vendor's patch.

## Is CVE-2026-74313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74313 is a high-severity use after free 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-74313 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-74313/ (Markdown: https://insights.sbomify.com/CVE-2026-74313/index.md)
```

## Sources

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

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