Linux: RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted
What fixes it
- 74c4ed55e61f1b65ddbebc5b635d136461a1c3daLinuxCVE List
- 6f8020fe7465f49e234a576c04e415e9d08c7878LinuxCVE List
- 31024e158b45358370a0a14ed96589e6aa62d6cbLinuxCVE List
- 8f253d5893f991742464b9e7203c43fc08d0aa11LinuxCVE List
- 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcdaLinuxCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted
The client borrows shared CQ credits in the ADDR_RESOLVED handler via ib_cq_pool_get(), before the peer is connected. create_cm() can return -ERESTARTSYS from wait_event_interruptible_timeout() without destroying the CM ID. The init_conns() and stop-and-destroy paths then call destroy_con_cq_qp() while cq is still NULL (no PUT) and only afterwards rdma_destroy_id().
CMA serializes the handler against rdma_destroy_id() with handler_mutex, but that does not order the GET against destroy_con_cq_qp(). If ADDR_RESOLVED has already passed the DESTROYING check, it can take con_mutex, GET credits, and then lose the con to kfree. Device unregister later hits WARN_ON(cq->cqe_used) in ib_cq_pool_cleanup().
Set a per-connection flag under con_mutex before CQ/QP teardown so a racing ADDR_RESOLVED cannot borrow credits after teardown has begun.
Text from CVE List
Affected versions 16
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before a82cca40139d9fcae8208901856bd5bb4051f097CVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before 74c4ed55e61f1b65ddbebc5b635d136461a1c3daCVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before 6f8020fe7465f49e234a576c04e415e9d08c7878CVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before 31024e158b45358370a0a14ed96589e6aa62d6cbCVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before 8f253d5893f991742464b9e7203c43fc08d0aa11CVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before bf88ac4867050112a6c819c8d1a7209bf48ef427CVE List
- Linuxaffected: 3b89e92c2a95a39c38a3808f4528e502a39bd94d before 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcdaCVE List
- Linuxaffected: 5.13CVE List
- Linuxunaffected: all versions before 5.13CVE List
- Linuxunaffected: 5.15.222 through 5.15.*CVE List
- Linuxunaffected: 6.1.189 through 6.1.*CVE List
- Linuxunaffected: 6.6.158 through 6.6.*CVE List
- Linuxunaffected: 6.12.112 through 6.12.*CVE List
- Linuxunaffected: 6.18.54 through 6.18.*CVE List
- Linuxunaffected: 7.2.8 through 7.2.*CVE List
- Linuxunaffected: 7.3CVE List
References 7
- git.kernel.org/stable/c/a82cca40139d9fcae8208901856bd5bb4051f097Referencevia CVE List
- git.kernel.org/stable/c/74c4ed55e61f1b65ddbebc5b635d136461a1c3daReferencevia CVE List
- git.kernel.org/stable/c/6f8020fe7465f49e234a576c04e415e9d08c7878Referencevia CVE List
- git.kernel.org/stable/c/31024e158b45358370a0a14ed96589e6aa62d6cbReferencevia CVE List
- git.kernel.org/stable/c/8f253d5893f991742464b9e7203c43fc08d0aa11Referencevia CVE List
- git.kernel.org/stable/c/bf88ac4867050112a6c819c8d1a7209bf48ef427Referencevia CVE List
- git.kernel.org/stable/c/2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcdaReferencevia CVE List