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-68418RDMA/irdma: Prevent user-triggered null deref on QP create

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent user-triggered null deref on QP create Previously, the user QP creation path would only attempt to populate iwqp->iwpbl if the user-provided req.user_wqe_bufs field was non-zero. The problem is that iwqp->iwpbl is unconditionally dereferenced later on in irdma_setup_virt_qp. While there was a check for iwqp->iwpbl != NULL, this check would only occur if req.user_wqe_bufs was non-zero. The end result is that a user could send a zero user_wqe_bufs value and trigger a null ptr deref. Fix this by unconditionally calling irdma_get_pbl and bailing if it fails, similar to the CQ and SRQ paths.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

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

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 (15 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 b48c24c2d710cf34810c555dcef883a3d35a9c08 – < 4e75028c000e9560a7ff66a23d7cd872a967ab7e
    • affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < d52ff592abfcd56234f266aa245c489f70b1c554
    • affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < ad68e0b759f9569f0dfea84f035c91eadb979802
    • affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < ec675b4cdfd378d8c9dd8c93126c024f2469bd79
    • affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < 728211c815f6eef28dd3df2a5b6297483185aa20
    • affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < b9b0889071569d43623c260074e159cd8f26adb1
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .