ALSA: pcm: Don't setup bogus iov_iter for silencing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The ALSA PCM interleaved copy path can create an invalid iov_iter when silencing data. On RISC-V, this can cause a NULL dereference. The input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running the Linux kernel on RISC-V should check whether their kernel includes the ALSA PCM fix; affected versions are not specified.