RDMA/umem: Fix double dma_buf_unpin in failure path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1e4df4a21c5ac722df1099eee30cad9246c889b5 · < 104016eb671e19709721c1b0048dd912dc2e96be| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/umem: Fix double dma_buf_unpin in failure path
In ib_umem_dmabuf_get_pinned_with_dma_device(), the call to ib_umem_dmabuf_map_pages() can fail. If this occurs, the dmabuf is immediately unpinned but the umem_dmabuf->pinned flag is still set. Then, when ib_umem_release() is called, it calls ib_umem_dmabuf_revoke() which will call dma_buf_unpin() again.
Fix this by removing the immediate unpin upon failure and just let the ib_umem_release/revoke path handle it. This also ensures the proper unmap-unpin unwind ordering if the dmabuf_map_pages call happened to fail due to dma_resv_wait_timeout (and therefore has a non-NULL umem_dmabuf->sgt).
From the CVE record · Linux
The Linux kernel’s RDMA/umem failure path can unpin a DMA buffer twice if mapping its pages fails. The buffer is unpinned immediately, then unpinned again during release because its pinned flag remains set. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with RDMA/umem should check their exposure; affected versions are not specified.