Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 3159c6fac43dc24b34d31971884d98a7a1bf4c4b, 4385ddd654d90245eeb83b3cb539670ab5c85ba4, 54cab78df0375196aaec4e3109191653d21751df.

Low priority for now. Upgrade to Linux Linux 3159c6fac43dc24b34d31971884d98a7a1bf4c4b, 4385ddd654d90245eeb83b3cb539670ab5c85ba4, 54cab78df0375196aaec4e3109191653d21751df or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74346

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.14affected
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before a80b3b13786e9ab1c52b31a1f16c7d6708fa9220affected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before 3159c6fac43dc24b34d31971884d98a7a1bf4c4baffected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before ad360a31092a870633ec255b96f50181628b4de0affected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before d566002de555b18cc395012c5c1cb8682fc6d2a9affected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before 54cab78df0375196aaec4e3109191653d21751dfaffected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before d5aa82da8f65562da996d184686db9d0ea718b91affected · git
    • b48c24c2d710cf34810c555dcef883a3d35a9c08 and later · before 4385ddd654d90245eeb83b3cb539670ab5c85ba4affected · git
    • before 5.14not affected · semver
    • 5.15.212 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74342Aug 15, 2026 · kernfs: link kn to its parent before the LSM init hook
    0Monitor
  • ← EarlierCVE-2026-74343Aug 15, 2026 · kernfs: fix xattr race condition with multiple superblocks
    31Monitor
  • Later →CVE-2026-74348Aug 15, 2026 · ocfs2/dlm: require a ref for locking_state debugfs open
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3159c6fac43dc24b34d31971884d98a7a1bf4c4bVendor (CNA)
Linux Linux4385ddd654d90245eeb83b3cb539670ab5c85ba4Vendor (CNA)
Linux Linux54cab78df0375196aaec4e3109191653d21751dfVendor (CNA)
Linux Linuxa80b3b13786e9ab1c52b31a1f16c7d6708fa9220Vendor (CNA)
Linux Linuxad360a31092a870633ec255b96f50181628b4de0Vendor (CNA)
Linux Linuxd566002de555b18cc395012c5c1cb8682fc6d2a9Vendor (CNA)
Linux Linuxd5aa82da8f65562da996d184686db9d0ea718b91Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records