RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bf88ac4867050112a6c819c8d1a7209bf48ef427, Kernel 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda, Kernel 31024e158b45358370a0a14ed96589e6aa62d6cb and 10 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <bf88ac4867050112a6c819c8d1a7209bf48ef427, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <31024e158b45358370a0a14ed96589e6aa62d6cb, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <6f8020fe7465f49e234a576c04e415e9d08c7878, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <74c4ed55e61f1b65ddbebc5b635d136461a1c3da, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <8f253d5893f991742464b9e7203c43fc08d0aa11, >=3b89e92c2a95a39c38a3808f4528e502a39bd94d <a82cca40139d9fcae8208901856bd5bb4051f097, =5.13 | bf88ac4867050112a6c819c8d1a7209bf48ef427, 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda, 31024e158b45358370a0a14ed96589e6aa62d6cb, 6f8020fe7465f49e234a576c04e415e9d08c7878, 74c4ed55e61f1b65ddbebc5b635d136461a1c3da, 8f253d5893f991742464b9e7203c43fc08d0aa11, a82cca40139d9fcae8208901856bd5bb4051f097 |
| linux-kernel: Kernel | >=5.16.0 <6.1.189, >=6.13.0 <6.18.54, >=6.19.0 <7.2.8, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=5.13.0 <5.15.222 | 6.1.189, 6.18.54, 7.2.8, 6.6.158, 6.12.112, 5.15.222 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket