CVE-2026-74613

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

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

vsock/virtio: avoid refilling the RX queue after teardown

Commit b917507e5ad9 ("vsock/virtio: stop workers during the .remove()") made the RX worker jump to its common exit when rx_run is clear. That exit still refills the RX queue when the buffer count is low, so work queued across virtio_vsock_vqs_del() can add buffers after the virtqueues have been deleted.

BUG: KASAN: slab-use-after-free in virtqueue_add_sgs Read of size 4 by task kworker/0:1 Workqueue: virtio_vsock virtio_transport_rx_work Call Trace: virtqueue_add_sgs (drivers/virtio/virtio_ring.c:2796) virtio_vsock_rx_fill (net/vmw_vsock/virtio_transport.c:332) virtio_transport_rx_work (net/vmw_vsock/virtio_transport.c:701) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) ... Freed by task 141: kfree (mm/slub.c:6566) vp_del_vq (drivers/virtio/virtio_pci_common.c:259) vp_del_vqs (drivers/virtio/virtio_pci_common.c:285) virtio_vsock_freeze (net/vmw_vsock/virtio_transport.c:912) virtio_device_freeze (drivers/virtio/virtio.c:658) virtio_pci_freeze (drivers/virtio/virtio_pci_common.c:601) pci_pm_freeze (drivers/pci/pci-driver.c:1098) device_suspend (drivers/base/power/main.c:1968) Kernel panic - not syncing: KASAN: panic_on_warn set ...

Jump to a no-refill exit when rx_run is clear, leaving the normal exit to replenish a running queue.

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

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (8)

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

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38c7763fdc533edb34dc8f4489c260e8ba2ccae9
generic

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d80a04129a6c27a690cb69de3fe3f50be5aa8b9
generic

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d37e3525cc346a1421c1bdeaad5848e249fc60c
generic

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock/virtio: avoid refilling the RX queue after teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a7658508f5fe8f1077a65e8cb9535d3426f37a2f

Vendor Advisories for CVE-2026-74613(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 04:53 UTCEG score recompute
  2. 2026-08-30 04:53 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 15:44 UTCGHSA enrichment
  5. 2026-08-29 02:35 UTCEG score recompute
  6. 2026-08-29 02:34 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 13:25 UTCGHSA enrichment
  9. 2026-08-28 00:16 UTCEG score recompute
  10. 2026-08-28 00:16 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 11:04 UTCGHSA enrichment
  13. 2026-08-26 21:55 UTCEG score recompute
  14. 2026-08-26 21:55 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:46 UTCGHSA enrichment
  17. 2026-08-25 19:37 UTCEG score recompute
  18. 2026-08-25 19:37 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 7.80
  23. 2026-08-25 05:45 UTCGHSA enrichment
  24. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · 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-74613?
CVE-2026-74613 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: avoid refilling the RX queue after teardown Commit b917507e5ad9 ("vsock/virtio: stop workers during the .remove()") made the RX worker jump to its common exit when rx_run is clear. That exit still refills the RX queue…
When was CVE-2026-74613 disclosed?
CVE-2026-74613 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-74613 actively exploited?
CVE-2026-74613 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-74613?
CVE-2026-74613 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74613, 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-74613

Explore →

Is Your Infrastructure Affected by CVE-2026-74613?

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