diff options
author | Lv Yunlong <lyl2019@mail.ustc.edu.cn> | 2021-04-25 18:16:47 -0700 |
---|---|---|
committer | Jason Gunthorpe <jgg@nvidia.com> | 2021-04-27 15:19:21 -0300 |
commit | 3093ee182f01689b89e9f8797b321603e5de4f63 (patch) | |
tree | ae8990dd3fe23814c0ef425b1dea8e21b89abeb4 /CREDITS | |
parent | 2d085ee1728e6ed52f63f221a8ac44cb744e7a84 (diff) | |
download | linux-stable-3093ee182f01689b89e9f8797b321603e5de4f63.tar.gz linux-stable-3093ee182f01689b89e9f8797b321603e5de4f63.tar.bz2 linux-stable-3093ee182f01689b89e9f8797b321603e5de4f63.zip |
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.
Fixes: 2251334dcac9 ("rdma/siw: application buffer management")
Link: https://lore.kernel.org/r/20210426011647.3561-1-lyl2019@mail.ustc.edu.cn
Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
Reviewed-by: Bernard Metzler <bmt@zurich.ihm.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions