RDMA: During rereg_mr ensure that REREG_ACCESS is compatible
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 09dc18894148381d3bfc550083b1236043870dce, Kernel 2904e985a2917b5dac65df82733065e78a65fc9d, Kernel 50334a05a950840b39a1ce3d2a173b4183db9b3e and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.2, >=b40656aa7d559adc1fe689396dc58b92a9a27286 <09dc18894148381d3bfc550083b1236043870dce, >=b40656aa7d559adc1fe689396dc58b92a9a27286 <2904e985a2917b5dac65df82733065e78a65fc9d, >=b40656aa7d559adc1fe689396dc58b92a9a27286 <50334a05a950840b39a1ce3d2a173b4183db9b3e, >=b40656aa7d559adc1fe689396dc58b92a9a27286 <badad6fad60def1b9805559dd81dbab3d97b82aa, >=b40656aa7d559adc1fe689396dc58b92a9a27286 <eba5df21eda0fe7418efbea2f799f8ea1b8ca94c | 09dc18894148381d3bfc550083b1236043870dce, 2904e985a2917b5dac65df82733065e78a65fc9d, 50334a05a950840b39a1ce3d2a173b4183db9b3e, badad6fad60def1b9805559dd81dbab3d97b82aa, eba5df21eda0fe7418efbea2f799f8ea1b8ca94c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket