CVE-2026-74346RDMA/irdma: Fix OOB read during CQ MR registration
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < a80b3b13786e9ab1c52b31a1f16c7d6708fa9220
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < 3159c6fac43dc24b34d31971884d98a7a1bf4c4b
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < ad360a31092a870633ec255b96f50181628b4de0
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < d566002de555b18cc395012c5c1cb8682fc6d2a9
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < 54cab78df0375196aaec4e3109191653d21751df
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < d5aa82da8f65562da996d184686db9d0ea718b91
- affected b48c24c2d710cf34810c555dcef883a3d35a9c08 – < 4385ddd654d90245eeb83b3cb539670ab5c85ba4
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/a80b3b13786e9ab1c52b31a1f16c7d6708fa9220 (opens in a new tab)
- https://git.kernel.org/stable/c/3159c6fac43dc24b34d31971884d98a7a1bf4c4b (opens in a new tab)
- https://git.kernel.org/stable/c/ad360a31092a870633ec255b96f50181628b4de0 (opens in a new tab)
- https://git.kernel.org/stable/c/d566002de555b18cc395012c5c1cb8682fc6d2a9 (opens in a new tab)
- https://git.kernel.org/stable/c/54cab78df0375196aaec4e3109191653d21751df (opens in a new tab)
- https://git.kernel.org/stable/c/d5aa82da8f65562da996d184686db9d0ea718b91 (opens in a new tab)
- https://git.kernel.org/stable/c/4385ddd654d90245eeb83b3cb539670ab5c85ba4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59493 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74346)Record last updated .