CVE-2026-74614

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
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.4Exploit: 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:

vsock/virtio: read virtqueues under worker locks

Commit bd50c5dc182b ("vsock/virtio: add support for device suspend/resume") made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX, TX and event workers read their virtqueue before locking and checking the corresponding flag, so a worker delayed across freeze and restore can observe the replacement queue's running state while retaining a pointer to the deleted queue.

Read each virtqueue under its mutex after checking the run flag, keeping the pointer and state in the same queue generation.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (7)

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

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1cecb4202afdbeddcf29d59baf596ac6ab753f7f
generic

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29dd10583bf9d2744cd84b862e4257c0a5699570
generic

vsock/virtio: read virtqueues under worker locks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/941329ce14c5f481223a10d1d4c8b57ea7f3048a

Vendor Advisories for CVE-2026-74614(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 25× in last 7d / 28× 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-30 02:18 UTCEG score recompute
  2. 2026-08-30 02:18 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 13:37 UTCGHSA enrichment
  5. 2026-08-29 00:53 UTCEG score recompute
  6. 2026-08-29 00:53 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 10:49 UTCGHSA enrichment
  9. 2026-08-27 22:06 UTCEG score recompute
  10. 2026-08-27 22:06 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 09:26 UTCGHSA enrichment
  13. 2026-08-26 20:46 UTCEG score recompute
  14. 2026-08-26 20:46 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 07:51 UTCGHSA enrichment
  17. 2026-08-25 19:10 UTCEG score recompute
  18. 2026-08-25 19:10 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:30 UTCEG score recompute
  21. 2026-08-25 06:30 UTCGHSA enrichment
  22. 2026-08-25 05:45 UTCEG score recompute▲ 8.40
  23. 2026-08-25 05:45 UTCGHSA enrichment
  24. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 3 more
  1. 2026-08-22 16:24 UTCNVD update
  2. 2026-08-22 15:42 UTCEG score recompute
  3. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74614?
CVE-2026-74614 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b ("vsock/virtio: add support for device suspend/resume") made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX,…
When was CVE-2026-74614 disclosed?
CVE-2026-74614 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74614 actively exploited?
CVE-2026-74614 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74614?
CVE-2026-74614 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-74614?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74614, 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-74614

Explore →

Is Your Infrastructure Affected by CVE-2026-74614?

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

Start Free Scan →Browse All CVEs