RDMA: During rereg_mr ensure that REREG_ACCESS is compatible
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA: During rereg_mr ensure that REREG_ACCESS is compatible
If IB_MR_REREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ib_umem_check_rereg() function that each driver has to call before processing IB_MR_REREG_ACCESS.
mlx4 has to retain its duplicate ib_access_writable check because it implements IB_MR_REREG_ACCESS | IB_MR_REREG_TRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination.
From the CVE record · Linux
In the Linux kernel's RDMA code, changing a memory region from read-only to read-write during re-registration can leave its underlying memory improperly pinned for writing. This occurs when a driver processes the access change without checking it. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with RDMA support should check their deployments; affected versions were not provided.