RDMA/umem: Fix double dma_buf_unpin in failure path

Summary

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).

Timeline

1. May 6, 2026, 11:27 AM UTCCVE published
2. Oct 16, 2026, 3:14 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Oct 19, 2026, 7:06 PM UTCRecord last updated

Affected versions

• Linux Linux

  From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in 70542b69abff34d24b11ae0bb200cc7a766d18df; From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in b324327ff6f48d8065dca67eb3b91357e72726bd; From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in ba3bf0f1bf1d5d0404678485e872980532fcc2c4; From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in d3e32e2f3262f1b25d77c085ace38e2cc4ad75cf; From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in 40126bcbefa79ea86672e05dae608596bab38319; From 1e4df4a21c5ac722df1099eee30cad9246c889b5 · fixed in 104016eb671e19709721c1b0048dd912dc2e96be

• Linux Linux

  5.16

• KernelLinux

  From 5.16.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6

References 6