CVE-2022-50543

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/rxe: Fix mr-&gt;map double free<br /> <br /> rxe_mr_cleanup() which tries to free mr-&gt;map again will be called when<br /> rxe_mr_init_user() fails:<br /> <br /> CPU: 0 PID: 4917 Comm: rdma_flush_serv Kdump: loaded Not tainted 6.1.0-rc1-roce-flush+ #25<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x45/0x5d<br /> panic+0x19e/0x349<br /> end_report.part.0+0x54/0x7c<br /> kasan_report.cold+0xa/0xf<br /> rxe_mr_cleanup+0x9d/0xf0 [rdma_rxe]<br /> __rxe_cleanup+0x10a/0x1e0 [rdma_rxe]<br /> rxe_reg_user_mr+0xb7/0xd0 [rdma_rxe]<br /> ib_uverbs_reg_mr+0x26a/0x480 [ib_uverbs]<br /> ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x1a2/0x250 [ib_uverbs]<br /> ib_uverbs_cmd_verbs+0x1397/0x15a0 [ib_uverbs]<br /> <br /> This issue was firstly exposed since commit b18c7da63fcb ("RDMA/rxe: Fix<br /> memory leak in error path code") and then we fixed it in commit<br /> 8ff5f5d9d8cf ("RDMA/rxe: Prevent double freeing rxe_map_set()") but this<br /> fix was reverted together at last by commit 1e75550648da (Revert<br /> "RDMA/rxe: Create duplicate mapping tables for FMRs")<br /> <br /> Simply let rxe_mr_cleanup() always handle freeing the mr-&gt;map once it is<br /> successfully allocated.