CVE-2026-74390

RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:59 AM UTC
Updated: October 16, 2026 at 08: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: Fix out-of-bounds write in irdma_copy_user_pgaddrs The irdma_copy_user_pgaddrs function loops through all of the umem DMA blocks to populate the PBLEs and will stop when either the last DMA block is reached or palloc->total_cnt is reached. The issue is that the logic for checking palloc->total_cnt would only work for non-zero values. When irdma_setup_pbles is called with lvl==0, it calls irdma_copy_user_pgaddrs with palloc->total_cnt==0, which means the only way to break out of the loop is to reach the last umem DMA block, which means it could end up going beyond the fixed size of 4 iwmr->pgaddrmem array that is used in the lvl==0 case. In the case of QP/CQ/SRQ rings, the value of lvl is determined by a separate input (for example, req.cq_pages in the case of a CQ). So, we must perform explicit checking to ensure we don't overflow the pgaddrmem array if the user provides a umem that consists of more blocks than their provided req.cq_pages.

Affected

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

5.14b48c24c2d710cf34810c555dcef883a3d35a9c08
Vendor states this is fixed in 192a3be0e3759daa24af2841208b074ca6dbaabc (fixed)
Vendor states this is fixed in 424d51d33c7541a86934067c2c0538124687fc90 (fixed)
Vendor states this is fixed in 4780f58672ee6328accd54a95f9c00683477e499 (fixed)
Vendor states this is fixed in 5ebb3ed757be3e04cf803026004aa0beaeb13e9b (fixed)
Vendor states this is fixed in 79a20a8e201a779224b4bf115250a7713bde72c0 (fixed)
Vendor states this is fixed in 9f8f0d2099e3de1194e37dc933ae0c4206b09aaf (fixed)
Vendor states this is fixed in abd27a977b419d584efa659488c22d2306987b29 (fixed)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (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

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