CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 35483c5306e09b3190ff937089d404a78012695c, 5c1560be8aa6849356455af67518d35c551cbd95, 79e12c891940b0c4c75881b7fd82a8cbb8ac97be.
Low priority for now. Upgrade to Linux Linux 35483c5306e09b3190ff937089d404a78012695c, 5c1560be8aa6849356455af67518d35c551cbd95, 79e12c891940b0c4c75881b7fd82a8cbb8ac97be or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before 35483c5306e09b3190ff937089d404a78012695caffected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before 5c1560be8aa6849356455af67518d35c551cbd95affected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before 93ed4692f2299a40346025979f40e4a9b7b33af7affected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before d94e2947203aead590fd63f667d316d4475d65afaffected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2affected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before 79e12c891940b0c4c75881b7fd82a8cbb8ac97beaffected · git
- c8a6153b6c59d95c0e091f053f6f180952ade91e and later · before e440e077748939839d9f76e24383b76b785f80ceaffected · git
- before 5.15not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74310Aug 15, 2026 · vhost/net: complete zerocopy ubufs only once37Monitor
- ← EarlierCVE-2026-74312Aug 15, 2026 · vhost/vdpa: validate virtqueue index in mmap and fault paths31Monitor
- Later →CVE-2026-74314Aug 15, 2026 · bpf: Cancel special fields on map value recycle31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 35483c5306e09b3190ff937089d404a78012695c | Vendor (CNA) |
| Linux Linux | 5c1560be8aa6849356455af67518d35c551cbd95 | Vendor (CNA) |
| Linux Linux | 79e12c891940b0c4c75881b7fd82a8cbb8ac97be | Vendor (CNA) |
| Linux Linux | 93ed4692f2299a40346025979f40e4a9b7b33af7 | Vendor (CNA) |
| Linux Linux | a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2 | Vendor (CNA) |
| Linux Linux | d94e2947203aead590fd63f667d316d4475d65af | Vendor (CNA) |
| Linux Linux | e440e077748939839d9f76e24383b76b785f80ce | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
- git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
- git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
- git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
- git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
- git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce
Vendor advisories and official records. Exploit/PoC links are deliberately left out.