RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs
Summary
| CVE | CVE-2026-74390 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:40 UTC |
| Updated | 2026-08-15 06:22:40 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 4780f58672ee6328accd54a95f9c00683477e499 git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 79a20a8e201a779224b4bf115250a7713bde72c0 git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 9f8f0d2099e3de1194e37dc933ae0c4206b09aaf git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 192a3be0e3759daa24af2841208b074ca6dbaabc git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 424d51d33c7541a86934067c2c0538124687fc90 git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 abd27a977b419d584efa659488c22d2306987b29 git |
Not specified |
| CNA |
Linux |
Linux |
affected b48c24c2d710cf34810c555dcef883a3d35a9c08 5ebb3ed757be3e04cf803026004aa0beaeb13e9b git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.14 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.14 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.212 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/abd27a977b419d584efa659488c22d2306987b29 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5ebb3ed757be3e04cf803026004aa0beaeb13e9b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9f8f0d2099e3de1194e37dc933ae0c4206b09aaf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4780f58672ee6328accd54a95f9c00683477e499 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/79a20a8e201a779224b4bf115250a7713bde72c0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/424d51d33c7541a86934067c2c0538124687fc90 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/192a3be0e3759daa24af2841208b074ca6dbaabc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.