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-68419RDMA/irdma: Prevent rereg_mr for non-mem regions

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent rereg_mr for non-mem regions When a QP/CQ/SRQ is created, a two step process is used where the buffer is allocated in userspace and explicitly registered with the normal reg_mr mechanism prior to creating the actual QP/CQ/SRQ object. These special registrations are indicated via an ABI field so the driver knows that they do not have a valid mkey and to skip the actual CQP command submission. Since these are real MR objects from the core's perspective, it is possible for a user application to invoke rereg_mr on them and cause a real CQP op to be emitted with the zero-initialized mkey value of 0. Fix this by preventing rereg_mr on these special regions.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 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-68419, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 715fdb3b30541cc8180b7cdc6aa9f8c307afdf25 – < fb46d134e1b8690bed2da9005b36d32d2efd34ac
    • affected 5ac388db27c443dadfbb0b8b23fa7ccf429d901a – < b5029e91c63406e4f4c8d58161048b41b6f0bd8c
    • affected 5ac388db27c443dadfbb0b8b23fa7ccf429d901a – < ca1c29f05274b737dc964e28b97803750d7cf7ec
    • affected 5ac388db27c443dadfbb0b8b23fa7ccf429d901a – < dbaa37e060918c45517786e37ecab0f300b48fa9
    • affected 5ac388db27c443dadfbb0b8b23fa7ccf429d901a – < a846aecb931b4d65d5eafa92a0623545af46d4f2
    • affected 6.6.120 – < 6.6.148
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .