Answer in brief
CVE-2026-64134 records a Unknown severity vulnerability in ALSA: pcm: Don't setup bogus iov_iter for silencing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cf393babb37a1679a1ec1d864df1090353465e23 <41a766c647294842c9b17672449f8e011048cba9 || >=cf393babb37a1679a1ec1d864df1090353465e23 <ce836587e594af39ff048d9b29dee0f5f10692c9 || >=cf393babb37a1679a1ec1d864df1090353465e23 <feff0251386aa6bb180a0a1cf7c1f91ba868113d || >=cf393babb37a1679a1ec1d864df1090353465e23 <c9f6768515818d71bdfc20119a81f3332c53b9c6 || >=cf393babb37a1679a1ec1d864df1090353465e23 <e4d3386b74fba8e01280484b67ee481ece00201e | 41a766c647294842c9b17672449f8e011048cba9, ce836587e594af39ff048d9b29dee0f5f10692c9, feff0251386aa6bb180a0a1cf7c1f91ba868113d, c9f6768515818d71bdfc20119a81f3332c53b9c6, e4d3386b74fba8e01280484b67ee481ece00201e |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 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. 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64134 records a Unknown severity vulnerability in ALSA: pcm: Don't setup bogus iov_iter for silencing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cf393babb37a1679a1ec1d864df1090353465e23 <41a766c647294842c9b17672449f8e011048cba9 || >=cf393babb37a1679a1ec1d864df1090353465e23 <ce836587e594af39ff048d9b29dee0f5f10692c9 || >=cf393babb37a1679a1ec1d864df1090353465e23 <feff0251386aa6bb180a0a1cf7c1f91ba868113d || >=cf393babb37a1679a1ec1d864df1090353465e23 <c9f6768515818d71bdfc20119a81f3332c53b9c6 || >=cf393babb37a1679a1ec1d864df1090353465e23 <e4d3386b74fba8e01280484b67ee481ece00201e | 41a766c647294842c9b17672449f8e011048cba9, ce836587e594af39ff048d9b29dee0f5f10692c9, feff0251386aa6bb180a0a1cf7c1f91ba868113d, c9f6768515818d71bdfc20119a81f3332c53b9c6, e4d3386b74fba8e01280484b67ee481ece00201e |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 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. 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.
Quoted source text, attributed separately from HOL analysis.