IB/mlx5: Properly support implicit ODP rereg_mr
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ef3642c4f54d3493c92c71faf46139b2473bc532 · < 5d02b9a2efd11d28d2a8feac7769686b1b871d9c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
IB/mlx5: Properly support implicit ODP rereg_mr
Due to all the child mkeys in the implicit ODP configuration we cannot change anything in place for the parent mkey. Instead the whole thing needs to be rebuilt if any change is requested. If the user does not specify a translation then force the implicit values which will then fall through the logic into mlx5_ib_reg_user_mr() to allocate a completely new MR.
Since implicit children were also touching the mr->pd, this removes another case where the access was racy.
From the CVE record · Linux
The Linux kernel's IB/mlx5 driver has a race involving implicit ODP memory-region re-registration and access to mr->pd. A local user who requests changes to an implicit ODP memory region can trigger the affected path; the input does not specify a further impact.
Engineers running Linux kernels that use IB/mlx5 implicit ODP should check their kernel versions against the vendor advisory; affected versions are not specified.