RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in a82cca40139d9fcae8208901856bd5bb4051f097; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in 74c4ed55e61f1b65ddbebc5b635d136461a1c3da; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in 6f8020fe7465f49e234a576c04e415e9d08c7878; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in 31024e158b45358370a0a14ed96589e6aa62d6cb; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in 8f253d5893f991742464b9e7203c43fc08d0aa11; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in bf88ac4867050112a6c819c8d1a7209bf48ef427; From 3b89e92c2a95a39c38a3808f4528e502a39bd94d · fixed in 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda
- Linux Linux
5.13
- KernelLinux
From 5.13.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 7
git.kernel.org
- stable/c/a82cca40139d9fcae8208901856bd5bb4051f097
- stable/c/74c4ed55e61f1b65ddbebc5b635d136461a1c3da
- stable/c/6f8020fe7465f49e234a576c04e415e9d08c7878
- stable/c/31024e158b45358370a0a14ed96589e6aa62d6cb
- stable/c/8f253d5893f991742464b9e7203c43fc08d0aa11
- stable/c/bf88ac4867050112a6c819c8d1a7209bf48ef427
- stable/c/2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda