CVE-2026-74313

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
generic

vduse: hold vduse_lock across IDR lookup in open path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c

Vendor Advisories for CVE-2026-74313(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 31× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 01:13 UTCEG score recompute
  2. 2026-08-21 01:13 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:02 UTCGHSA enrichment
  5. 2026-08-20 02:45 UTCEG score recompute
  6. 2026-08-20 02:45 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 15:34 UTCGHSA enrichment
  9. 2026-08-19 04:12 UTCGHSA enrichment
  10. 2026-08-18 17:00 UTCEG score recompute
  11. 2026-08-18 17:00 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 04:51 UTCGHSA enrichment
  15. 2026-08-17 17:40 UTCEG score recompute
  16. 2026-08-17 17:40 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:27 UTCEG score recompute
  19. 2026-08-17 06:27 UTCGHSA enrichment
  20. 2026-08-17 05:56 UTCEG score recompute▲ 8.80
  21. 2026-08-17 05:56 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  23. 2026-08-17 05:27 UTCEG score recompute
  24. 2026-08-17 05:27 UTCGHSA enrichment
  25. 2026-08-17 05:25 UTCMITRE cvelistV5
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:16 UTCEG score recompute
  6. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74313?
CVE-2026-74313 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: vduse: hold vduse_lock across IDR lookup in open path vdusedevopen() 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…
When was CVE-2026-74313 disclosed?
CVE-2026-74313 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74313 actively exploited?
CVE-2026-74313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74313?
CVE-2026-74313 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74313, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74313

Explore →

Is Your Infrastructure Affected by CVE-2026-74313?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs