RDMA/siw: Fix a use after free in siw_alloc_mr
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3093ee182f01689b89e9f8797b321603e5de4f63, Kernel 30b9e92d0b5e5d5dc1101ab856c17009537cbca4, Kernel 3e22b88e02c194f6c80867abfef5cc09383461f4 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.3, >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3093ee182f01689b89e9f8797b321603e5de4f63, >=2251334dcac9eb337575d8767e2a6a7e81848f7f <30b9e92d0b5e5d5dc1101ab856c17009537cbca4, >=2251334dcac9eb337575d8767e2a6a7e81848f7f <3e22b88e02c194f6c80867abfef5cc09383461f4, >=2251334dcac9eb337575d8767e2a6a7e81848f7f <608a4b90ece039940e9425ee2b39c8beff27e00c, >=2251334dcac9eb337575d8767e2a6a7e81848f7f <ad9ce7188432650469a6c7625bf479f5ed0b6155 | 3093ee182f01689b89e9f8797b321603e5de4f63, 30b9e92d0b5e5d5dc1101ab856c17009537cbca4, 3e22b88e02c194f6c80867abfef5cc09383461f4, 608a4b90ece039940e9425ee2b39c8beff27e00c, ad9ce7188432650469a6c7625bf479f5ed0b6155 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket