Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98352

RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < a82cca40139d9fcae8208901856bd5bb4051f097
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < 74c4ed55e61f1b65ddbebc5b635d136461a1c3da
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < 6f8020fe7465f49e234a576c04e415e9d08c7878
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < 31024e158b45358370a0a14ed96589e6aa62d6cb
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < 8f253d5893f991742464b9e7203c43fc08d0aa11
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < bf88ac4867050112a6c819c8d1a7209bf48ef427
    • affected 3b89e92c2a95a39c38a3808f4528e502a39bd94d – < 2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98352 badge
[![CVE-2026-98352](https://cveledger.app/badge/CVE-2026-98352.svg)](https://cveledger.app/cve/CVE-2026-98352)

Record last updated .