CVE-2026-64134

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: pcm: Don't setup bogus iov_iter for silencing

At transition to the iov_iter for PCM data transfer, we blindly applied the iov_iter setup also for silencing (i.e. data = NULL), and it leads to a calculation of bogus iov_iter. Fortunately this didn't cause troubles on most of architectures but it goes wrong on RISC-V now, causing a NULL dereference.

Handle the NULL data case to treat the silencing in interleaved_copy() for addressing the bug above. noninterleaved_copy() has already the NULL data handling, so it doesn't need changes.

CVSS v3
7.8
EG Score
7.8(medium)
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

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (5)

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

ALSA: pcm: Don't setup bogus iov_iter for silencing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: Don't setup bogus iov_iter for silencing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: Don't setup bogus iov_iter for silencing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: Don't setup bogus iov_iter for silencing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: Don't setup bogus iov_iter for silencing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41a766c647294842c9b17672449f8e011048cba9

Vendor Advisories for CVE-2026-64134(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 31× in last 7d / 171× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64134?
CVE-2026-64134 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus iov_iter for silencing At transition to the iov_iter for PCM data transfer, we blindly applied the iov_iter setup also for silencing (i.e. data = NULL), and it leads to a calculation of bogus iov_iter.…
When was CVE-2026-64134 disclosed?
CVE-2026-64134 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64134 actively exploited?
CVE-2026-64134 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64134?
CVE-2026-64134 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64134?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64134, 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-64134

Explore →

Is Your Infrastructure Affected by CVE-2026-64134?

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

Start Free Scan →Browse All CVEs