RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 30353bfc43a1602c020f31d95cf27182ffd23824 · < c9341307ea16b9395c2e4c9c94d8499d91fe31d0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()
Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will crash if an event is delivered before the srq object is finished initializing.
Use the spinlock since it isn't easy to make RCU work, use refcount_inc_not_zero() to protect against partially initialized objects, and order the refcount_set() to be after the srq is fully initialized.
From the CVE record · Linux
The Linux kernel’s RDMA/mlx4 driver misuses RCU when handling SRQ events. An event delivered before an SRQ object finishes initializing can cause a crash; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the RDMA/mlx4 driver should check their systems; affected versions are not specified.