CVE-2026-74346

RDMA/irdma: Fix OOB read during CQ MR registration

N/A
Published: August 15, 2026 at 05:58 AM UTC
Updated: August 17, 2026 at 06:19 AM 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix OOB read during CQ MR registration Sashiko pointed out an unrelated bug during a previous patch: https://sashiko.dev/#/patchset/20260512183852.614045-1-jmoroni%40google.com This change fixes the bug by eliminating the cqmr->split field which was not being set properly and instead just checks the CQ resize feature flag directly. The cqmr->split field essentially tracks whether IRDMA_FEATURE_CQ_RESIZE is set, but it was not being set until CQ creation time, which is _after_ CQ memory registration (the only other place where it is referenced). As a result, it would always be false during MR registration and would therefore cause irdma_handle_q_mem to populate cqmr->shadow even for GEN_2 HW and beyond: cqmr->shadow = (dma_addr_t)arr[req->cq_pages]; The issue is that for GEN_2 and beyond, req->cq_pages may be exactly equal to iwmr->page_cnt and therefore equal to the size of arr, which would cause an OOB read by one.

Affected

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

5.14 ≤ v < 5.15.2125.14 ≤ v < 6.1.1785.14 ≤ v < 6.12.975.14 ≤ v < 6.18.405.14 ≤ v < 6.6.1455.14 ≤ v < 7.1.55.14 ≤ v < 7.25.14b48c24c2d710cf34810c555dcef883a3d35a9c08
Vendor states this is fixed in 3159c6fac43dc24b34d31971884d98a7a1bf4c4b (fixed)
Vendor states this is fixed in 4385ddd654d90245eeb83b3cb539670ab5c85ba4 (fixed)
Vendor states this is fixed in 54cab78df0375196aaec4e3109191653d21751df (fixed)
Vendor states this is fixed in a80b3b13786e9ab1c52b31a1f16c7d6708fa9220 (fixed)
Vendor states this is fixed in ad360a31092a870633ec255b96f50181628b4de0 (fixed)
Vendor states this is fixed in d566002de555b18cc395012c5c1cb8682fc6d2a9 (fixed)
Vendor states this is fixed in d5aa82da8f65562da996d184686db9d0ea718b91 (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.

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