CVE-2026-68419

RDMA/irdma: Prevent rereg_mr for non-mem regions

HIGH
7.8
CVSS Score
Published: August 10, 2026 at 12:04 PM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5ac388db27c443dadfbb0b8b23fa7ccf429d901a6.6.1206.7715fdb3b30541cc8180b7cdc6aa9f8c307afdf25
Vendor states this is fixed in a846aecb931b4d65d5eafa92a0623545af46d4f2 (fixed)
Vendor states this is fixed in b5029e91c63406e4f4c8d58161048b41b6f0bd8c (fixed)
Vendor states this is fixed in ca1c29f05274b737dc964e28b97803750d7cf7ec (fixed)
Vendor states this is fixed in dbaa37e060918c45517786e37ecab0f300b48fa9 (fixed)
Vendor states this is fixed in fb46d134e1b8690bed2da9005b36d32d2efd34ac (fixed)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card