RDMA/siw: Fix a use after free in siw_alloc_mr
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/siw: Fix a use after free in siw_alloc_mr
Our code analyzer reported a UAF.
In siw_alloc_mr(), it calls siw_mr_add_mem(mr,..). In the implementation of siw_mr_add_mem(), mem is assigned to mr->mem and then mem is freed via kfree(mem) if xa_alloc_cyclic() failed. Here, mr->mem still point to a freed object. After, the execution continue up to the err_out branch of siw_alloc_mr, and the freed mr->mem is used in siw_mr_drop_mem(mr).
My patch moves "mr->mem = mem" behind the if (xa_alloc_cyclic(..)<0) {} section, to avoid the uaf.
From the CVE record · Linux
The Linux kernel’s RDMA/siw code can use freed memory when memory registration fails during allocation. If xa_alloc_cyclic() fails, siw_alloc_mr() may pass a freed pointer to siw_mr_drop_mem(). The report does not establish whether an attacker can trigger this condition or what access or user interaction it requires.
Engineers running the Linux kernel should check whether their version includes the RDMA/siw fix; affected versions are not specified.