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-31565RDMA/irdma: Fix deadlock during netdev reset with active connections

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix deadlock during netdev reset with active connections Resolve deadlock that occurs when user executes netdev reset while RDMA applications (e.g., rping) are active. The netdev reset causes ice driver to remove irdma auxiliary driver, triggering device_delete and subsequent client removal. During client removal, uverbs_client waits for QP reference count to reach zero while cma_client holds the final reference, creating circular dependency and indefinite wait in iWARP mode. Skip QP reference count wait during device reset to prevent deadlock.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 7 months 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

CVSS scores of CVE-2026-31565, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0b3c392b82cdf867808a8ea7c6760d3c7e6b6627 – < 009831768faeca3fb5950ce63f1b49594ec82389
    • affected 07322c8a12d6c796450faacb8be9e5e3c278ec84 – < adf0de36e52a48681eb58cbd7cbf6c8d200caa2b
    • affected c8f304d75f6c6cc679a73f89591f9a915da38f09 – < acb060bc2609c2eab49263968be59c7d59d497bc
    • affected c8f304d75f6c6cc679a73f89591f9a915da38f09 – < a8a1c7621127a15a02494b96ee376406c064237b
    • affected c8f304d75f6c6cc679a73f89591f9a915da38f09 – < cd8bcec2de5e24e05c34c9391940fda6f50e79b4
    • affected c8f304d75f6c6cc679a73f89591f9a915da38f09 – < 464bbb844ba5b68e038220c34019069a0a9f1581
    • affected c8f304d75f6c6cc679a73f89591f9a915da38f09 – < 6f52370970ac07d352a7af4089e55e0e6425f827
    • affected 6ee53f82540769a6d6e77e40b901f9b9edfa5ff2
    • affected 5.15.116 – < 5.15.203
    • affected 6.1.33 – < 6.1.168
    • affected 6.3.7 – < 6.4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .