CVE-2026-74312

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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:

vhost/vdpa: validate virtqueue index in mmap and fault paths

vhost_vdpa_mmap() and vhost_vdpa_fault() use vma->vm_pgoff as a virtqueue index for get_vq_notification(), but they do not validate that the index is smaller than v->nvqs.

The ioctl path already performs both a bounds check and array_index_nospec(), but the mmap/fault path only checks that the index fits in u16. This allows an out-of-range queue index to reach driver-specific get_vq_notification() callbacks.

Fix this by extracting a unified vhost_vdpa_get_vq_notification() helper that validates the queue index against v->nvqs and applies array_index_nospec() before calling the driver callback. Both the mmap and fault paths use this helper, and the bounds checking is consolidated into a single location.

From source inspection, the most defensible impact is out-of-bounds access in the callback path, potentially leading to invalid PFN remaps and crash/DoS.

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 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/929e4f044621c8cc30b612fb74e1410bef09e41b
generic

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55a644031e610ea93fbde2702c7b8f267476552f
generic

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d
generic

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b3f79b90b231a682315fe2191bb71925650e183
generic

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

vhost/vdpa: validate virtqueue index in mmap and fault paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f310bac6db9bd3bb1655707d692d9d2a86eeb17

Vendor Advisories for CVE-2026-74312(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 27× in last 7d / 27× 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-20 01:07 UTCEG score recompute
  2. 2026-08-20 01:07 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 14:01 UTCGHSA enrichment
  5. 2026-08-19 02:52 UTCGHSA enrichment
  6. 2026-08-18 15:46 UTCEG score recompute
  7. 2026-08-18 15:45 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 04:39 UTCGHSA enrichment
  11. 2026-08-17 17:33 UTCEG score recompute
  12. 2026-08-17 17:33 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:27 UTCEG score recompute
  15. 2026-08-17 06:27 UTCGHSA enrichment
  16. 2026-08-17 05:56 UTCEG score recompute 7.80
  17. 2026-08-17 05:56 UTCGHSA enrichment
  18. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-08-17 05:27 UTCEG score recompute
  20. 2026-08-17 05:27 UTCGHSA enrichment
  21. 2026-08-17 05:24 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 06:23 UTCNVD update
Show 2 more
  1. 2026-08-15 06:16 UTCEG score recompute
  2. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74312?
CVE-2026-74312 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: vhost/vdpa: validate virtqueue index in mmap and fault paths vhostvdpammap() and vhostvdpafault() use vma->vm_pgoff as a virtqueue index for getvqnotification(), but they do not validate that the index is smaller than v->nvqs. The…
When was CVE-2026-74312 disclosed?
CVE-2026-74312 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-74312 actively exploited?
CVE-2026-74312 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74312?
CVE-2026-74312 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74312, 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-74312

Explore →

Is Your Infrastructure Affected by CVE-2026-74312?

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