RDMA/irdma: Fix double free related to rereg_user_mr
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/irdma: Fix double free related to rereg_user_mr
If IB_MR_REREG_TRANS is set during rereg_user_mr, the umem will be released and a new one will be allocated in irdma_rereg_mr_trans. If any step of irdma_rereg_mr_trans fails after the new umem is allocated, it releases the umem, but does not set iwmr->region to NULL. The problem is that this failure is propagated to the user, who will then call ibv_dereg_mr (as they should). Then, the dereg_mr path will see a non-NULL umem and attempt to call ib_umem_release again.
Fix this by setting iwmr->region to NULL after ib_umem_release.
Fixed: 5ac388db27c4 ("RDMA/irdma: Add support to re-register a memory region")
From the CVE record · Linux
The Linux kernel RDMA/irdma driver can release a memory region’s umem twice. This can occur when a user re-registers a memory region with IB_MR_REREG_TRANS, an allocation step fails, and the user then deregisters the region. The described path requires local user interaction; the input does not specify whether authentication is required.
Engineers running Linux kernels with the RDMA/irdma driver should check for the affected code; affected versions are not specified.