CVE-2026-74313
Received Received - Intake

BaseFortify

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
CVE-2026-74313
EUVD
EUVD-2026-59460

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel's vduse subsystem. The issue occurs in the vduse_dev_open() function where a race condition exists between opening a device and destroying it. The open path releases vduse_lock before acquiring dev->lock, allowing a concurrent destroy operation to free the device while it is still being accessed, leading to memory corruption.

Detection Guidance

This vulnerability is specific to the Linux kernel's vduse subsystem and requires kernel-level inspection. Detection involves checking kernel logs for use-after-free errors or monitoring for crashes in vduse-related processes. No direct network detection commands are applicable.

Impact Analysis

This vulnerability could allow an attacker with local access to trigger a use-after-free condition, potentially causing system crashes, privilege escalation, or arbitrary code execution. Systems using VDUSE (vDPA Device in Userspace) features may be affected.

Mitigation Strategies

Apply the latest kernel patches from your Linux distribution to resolve the vduse_lock race condition. If immediate patching is not possible, consider disabling the vduse module via kernel parameters (e.g., adding vduse.enable=0 to boot parameters) until updates are applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74313. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart