CVE-2026-64490

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 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:

ALSA: virtio: Validate control metadata from the device

virtio-snd control handling trusts the device-provided control type and value count returned by the device.

That metadata is then used directly to index g_v2a_type_map[] in virtsnd_kctl_info(), and to size loops and memcpy() operations in virtsnd_kctl_get() and virtsnd_kctl_put() against fixed-size virtio_snd_ctl_value and snd_ctl_elem_value arrays.

A buggy or malicious device can therefore trigger out-of-bounds access by advertising an invalid control type or an oversized value count.

Validate control type and count once in virtsnd_kctl_parse_cfg(), before querying enumerated items or exposing the control to ALSA.

CVSS v3
8.4
EG Score
8.4(medium)
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
5%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 27, 2026

Advisory Details (4)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

ALSA: virtio: Validate control metadata from the device - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: virtio: Validate control metadata from the device - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: virtio: Validate control metadata from the device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3243563f99ef5d3949b934bd6390a5679405d0e1
generic

ALSA: virtio: Validate control metadata from the device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21584672fd699abe1768241d6c501b2de6139b6a

Vendor Advisories for CVE-2026-64490(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 15× in last 7d / 15× 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-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 05:26 UTCEG score recompute
  3. 2026-07-27 05:26 UTCGHSA enrichment
  4. 2026-07-27 05:13 UTCEG score recompute▲ 8.40
  5. 2026-07-27 05:13 UTCGHSA enrichment
  6. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 02:46 UTCEG score recompute
  10. 2026-07-26 02:46 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 10:39 UTCNVD update
  14. 2026-07-25 09:25 UTCEG score recompute
  15. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64490?
CVE-2026-64490 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: virtio: Validate control metadata from the device virtio-snd control handling trusts the device-provided control type and value count returned by the device. That metadata is then used directly to index gv2atype_map[] in…
When was CVE-2026-64490 disclosed?
CVE-2026-64490 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64490 actively exploited?
CVE-2026-64490 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64490?
CVE-2026-64490 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-64490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64490, 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-64490

Explore →

Is Your Infrastructure Affected by CVE-2026-64490?

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

Start Free Scan →Browse All CVEs