KernelScan.io

HIGH Introduced in 5.14

irdma RingMR UAF

CVE-2026-93154

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.8HIGH

01

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Add refcounting to user ring MRs Prevent userspace from deregistering the MRs that back QP/CQ/SRQ rings by bumping the MR's refcount upon association.

02

Engine v0.6.0

Risk summary

A local user with access to an Intel RDMA device (irdma driver) can trigger a use-after-free by deregistering memory regions that still back active QP/CQ/SRQ rings. This can lead to kernel memory corruption, potentially resulting in privilege escalation or a system crash. The vulnerability requires the irdma driver and compatible RDMA hardware to be present.

Affecteddrivers/infiniband/hw/irdma/verbs.c, drivers/infiniband/hw/irdma/utils.c (RDMA/irdma)

Vulnerability analysis

A local user with access to an Intel RDMA device can deregister memory regions that are still backing active QP, CQ, or SRQ ring structures. Because the original code does not hold a reference count on the memory region when it is associated with a ring, the deregistration frees the region's resources while the kernel still references it through the ring, resulting in a use-after-free when the ring subsequently accesses the freed memory. The fix adds a per-MR reference count that is incremented each time the MR is bound to a ring and decremented when that ring is torn down, so the memory region cannot be freed until all rings using it have been released. The vulnerable path is reachable from userspace through the RDMA verbs API on a system with the irdma driver loaded and compatible Intel RDMA hardware present; it requires only ordinary local device access, not root privileges.

03

BranchIntroducedFixed inPatch commit
6.185.146.18.5207974c267f60
7.25.147.2.6a6c0e693a7c8
mainline5.147.3f67d8a08f60c

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Affected — no CIP fix yet (latest 6.12.112-cip33)
cip/6.1Affected — no CIP fix yet (latest 6.1.189-cip61)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)