misc: fastrpc: Remove buffer from list prior to unmap operation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2419e55e532de14fdf336e09e453aa2831c73a25 · < 9bf22a7d950cec2d1efeca7f16bb20fcca84c36a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc: fastrpc: Remove buffer from list prior to unmap operation
fastrpc_req_munmap_impl() is called to unmap any buffer. The buffer is getting removed from the list after it is unmapped from DSP. This can create potential race conditions if multiple threads invoke unmap concurrently, where one thread may remove the entry from the list while another thread's unmap operation is still ongoing.
Fix this by removing the buffer entry from the list before calling the unmap operation. If the unmap fails, the entry is re-added to the list so that userspace can retry the unmap, or alternatively, the buffer will be cleaned up during device release when the DSP process is torn down and all DSP-side mappings are freed along with remaining buffers in the list.
From the CVE record · Linux
The Linux kernel’s fastrpc buffer-unmapping code removes a buffer from its list after unmapping it from the DSP. Concurrent unmap calls from multiple threads can race, allowing one thread to remove the entry while another unmap is still in progress.
Engineers running Linux kernels with the fastrpc component should check whether their kernel includes the fix; affected versions were not specified.