ALSA: us122l: Prevent write upgrades for read mappings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 030a07e441296c372f946cd4065b5d831d8dc40c · < d9c537b14f4982f17b103e3a2cfeee4bee6bc026| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: us122l: Prevent write upgrades for read mappings
The hwdep mmap callback rejects read-buffer mappings that are initially writable, but leaves VM_MAYWRITE set on mappings created with PROT_READ. A process that can open the hwdep node O_RDWR can later use mprotect() to make the mapping writable.
The read allocation begins with struct usb_stream. Its read_size member is used by the fault handler to decide which pages belong to the read buffer. The read VMA intentionally remains expandable because pcm_usb_stream uses mremap() after reading that size. Changing read_size first can therefore map and access pages beyond the allocation. The same member is also consumed by usb_stream_free(), where changing it can make free_pages_exact() release pages outside the allocation.
Clear VM_MAYWRITE for read-buffer mappings after rejecting an initially writable VMA. This keeps the separate output-buffer mapping writable while preventing later permission upgrades.
From the CVE record · Linux
ALSA us122l read-buffer mappings can be made writable after they are created read-only. A local process that can open the hwdep node with O_RDWR can use mprotect() to change the mapping, potentially accessing pages beyond the allocation or causing pages outside it to be freed.
Engineers running Linux kernels with the ALSA us122l driver should check whether their kernel is affected; affected versions were not provided.