RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, Kernel 2d8b30b496bc53e961ba7415fd629fc27813017c, Kernel 654aeddbc6e0f6e56531985bb12328ab4230c6c1 and 3 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.9, >=30353bfc43a1602c020f31d95cf27182ffd23824 <1e2a44875b6afb4add1115f7f3351dcbeb6f273d, >=30353bfc43a1602c020f31d95cf27182ffd23824 <2d8b30b496bc53e961ba7415fd629fc27813017c, >=30353bfc43a1602c020f31d95cf27182ffd23824 <654aeddbc6e0f6e56531985bb12328ab4230c6c1, >=30353bfc43a1602c020f31d95cf27182ffd23824 <8b7833f3bce35cb0d01c1503781523c099c675f0, >=30353bfc43a1602c020f31d95cf27182ffd23824 <c9341307ea16b9395c2e4c9c94d8499d91fe31d0, >=30353bfc43a1602c020f31d95cf27182ffd23824 <f0dbd9355ce1e93808541260c7ffab7956df9233 | 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, 2d8b30b496bc53e961ba7415fd629fc27813017c, 654aeddbc6e0f6e56531985bb12328ab4230c6c1, 8b7833f3bce35cb0d01c1503781523c099c675f0, c9341307ea16b9395c2e4c9c94d8499d91fe31d0, f0dbd9355ce1e93808541260c7ffab7956df9233 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket