CVE-2026-64490

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. 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

A fix is available — apply it.

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

August 17, 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

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 28× in last 7d / 105× 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.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-09-18 19:36 UTCEG score recompute
  2. 2026-09-18 19:36 UTCVendor advisory
  3. 2026-09-18 19:36 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 02:40 UTCEG score recompute
  6. 2026-09-18 02:40 UTCVendor advisory
  7. 2026-09-18 02:40 UTCGHSA enrichment
  8. 2026-09-17 01:50 UTCEG score recompute
  9. 2026-09-17 01:50 UTCVendor advisory
  10. 2026-09-17 01:50 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 06:24 UTCEG score recompute
  13. 2026-09-16 06:24 UTCVendor advisory
  14. 2026-09-16 06:24 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 09:19 UTCEG score recompute
  17. 2026-09-15 09:19 UTCVendor advisory
  18. 2026-09-15 09:19 UTCGHSA enrichment
  19. 2026-09-14 10:15 UTCVendor advisory
  20. 2026-09-14 10:15 UTCGHSA enrichment
  21. 2026-09-13 21:23 UTCEG score recompute
  22. 2026-09-13 21:23 UTCVendor advisory
  23. 2026-09-13 21:23 UTCGHSA enrichment
  24. 2026-09-13 06:59 UTCVendor advisory
  25. 2026-09-13 06:59 UTCGHSA enrichment
Show 75 more
  1. 2026-09-12 17:58 UTCEG score recompute
  2. 2026-09-12 17:58 UTCVendor advisory
  3. 2026-09-12 17:58 UTCGHSA enrichment
  4. 2026-09-12 05:10 UTCVendor advisory
  5. 2026-09-12 05:09 UTCGHSA enrichment
  6. 2026-09-11 16:20 UTCEG score recompute
  7. 2026-09-11 16:20 UTCVendor advisory
  8. 2026-09-11 16:20 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-11 02:09 UTCVendor advisory
  12. 2026-09-11 02:08 UTCGHSA enrichment
  13. 2026-09-10 10:26 UTCEG score recompute
  14. 2026-09-10 10:26 UTCVendor advisory
  15. 2026-09-10 10:25 UTCGHSA enrichment
  16. 2026-09-09 08:30 UTCEG score recompute
  17. 2026-09-09 08:30 UTCVendor advisory
  18. 2026-09-09 08:30 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 21:11 UTCEG score recompute
  21. 2026-09-07 21:11 UTCVendor advisory
  22. 2026-09-07 21:11 UTCGHSA enrichment
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-07 00:01 UTCEG score recompute
  25. 2026-09-07 00:01 UTCVendor advisory
  26. 2026-09-07 00:01 UTCGHSA enrichment
  27. 2026-09-06 13:47 UTCEPSS rescore
  28. 2026-09-06 08:07 UTCVendor advisory
  29. 2026-09-06 08:07 UTCGHSA enrichment
  30. 2026-09-05 19:18 UTCEG score recompute
  31. 2026-09-05 19:18 UTCVendor advisory
  32. 2026-09-05 19:18 UTCGHSA enrichment
  33. 2026-09-05 15:31 UTCEPSS rescore
  34. 2026-09-05 05:54 UTCEG score recompute
  35. 2026-09-05 05:54 UTCVendor advisory
  36. 2026-09-05 05:54 UTCGHSA enrichment
  37. 2026-09-04 12:38 UTCEG score recompute
  38. 2026-09-04 12:38 UTCVendor advisory
  39. 2026-09-04 12:38 UTCGHSA enrichment
  40. 2026-09-04 05:07 UTCEPSS rescore
  41. 2026-09-02 14:12 UTCEPSS rescore
  42. 2026-09-01 23:07 UTCEG score recompute
  43. 2026-09-01 23:07 UTCGHSA enrichment
  44. 2026-09-01 13:54 UTCEPSS rescore
  45. 2026-08-31 01:43 UTCEG score recompute
  46. 2026-08-31 01:43 UTCGHSA enrichment
  47. 2026-08-30 19:17 UTCEPSS rescore
  48. 2026-08-30 12:54 UTCEG score recompute
  49. 2026-08-30 12:54 UTCGHSA enrichment
  50. 2026-08-30 01:22 UTCEPSS rescore
  51. 2026-08-30 00:01 UTCEG score recompute
  52. 2026-08-30 00:01 UTCGHSA enrichment
  53. 2026-08-28 21:42 UTCEPSS rescore
  54. 2026-08-28 01:28 UTCEG score recompute
  55. 2026-08-28 01:28 UTCGHSA enrichment
  56. 2026-08-27 12:18 UTCGHSA enrichment
  57. 2026-08-26 23:29 UTCEG score recompute
  58. 2026-08-26 23:29 UTCGHSA enrichment
  59. 2026-08-26 14:47 UTCEPSS rescore
  60. 2026-08-26 10:38 UTCGHSA enrichment
  61. 2026-08-25 20:46 UTCEG score recompute
  62. 2026-08-25 20:46 UTCGHSA enrichment
  63. 2026-08-25 13:49 UTCEPSS rescore
  64. 2026-08-25 07:56 UTCGHSA enrichment
  65. 2026-08-24 19:08 UTCEG score recompute
  66. 2026-08-24 19:08 UTCGHSA enrichment
  67. 2026-08-24 06:17 UTCGHSA enrichment
  68. 2026-08-23 17:29 UTCGHSA enrichment
  69. 2026-08-23 04:41 UTCEG score recompute
  70. 2026-08-23 04:40 UTCGHSA enrichment
  71. 2026-08-23 00:19 UTCEPSS rescore
  72. 2026-08-22 15:52 UTCGHSA enrichment
  73. 2026-08-22 02:57 UTCEG score recompute
  74. 2026-08-22 02:56 UTCGHSA enrichment
  75. 2026-08-21 23:49 UTCEPSS rescore

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 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-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.2% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.