CVE-2026-64134
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://git.kernel.org/stable/c/41a766c647294842c9b17672449f8e011048cba9
- https://git.kernel.org/stable/c/c9f6768515818d71bdfc20119a81f3332c53b9c6
- https://git.kernel.org/stable/c/ce836587e594af39ff048d9b29dee0f5f10692c9
- https://git.kernel.org/stable/c/e4d3386b74fba8e01280484b67ee481ece00201e
- https://git.kernel.org/stable/c/feff0251386aa6bb180a0a1cf7c1f91ba868113d
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.