CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size
Noroxi assessment
Priority: Monitor (action score 31/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).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 42f3d2c8c18b92ea33e506a38b64f1a8986c2823, 4b87a2497276a72fd63028e7419abf0fb7ed837b, 6fc874fdfb366bfb11c62e6af9a831c8be59ddda.
Low priority for now. Upgrade to Linux Linux 42f3d2c8c18b92ea33e506a38b64f1a8986c2823, 4b87a2497276a72fd63028e7419abf0fb7ed837b, 6fc874fdfb366bfb11c62e6af9a831c8be59ddda 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/mlx5: Fix undefined shift of user RQ WQE size set_rq_size() computes the RQ WQE size as "1 << rq_wqe_shift" based on the user-provided rq_wqe_shift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shift of 31 also overflows a signed integer, leading to undefined behavior. Use check_shl_overflow() to compute the RQ WQE size and reject any invalid values.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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
- 3.11affected
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 9fff54929cc00849d738faa99f06c32399aeb026affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before b746f949c2ac2b041102836095d6d4a2ef21fa75affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before c1dbf52d24a8cb1aa56780ba51b72e7d495f258caffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 6fc874fdfb366bfb11c62e6af9a831c8be59dddaaffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 42f3d2c8c18b92ea33e506a38b64f1a8986c2823affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 4b87a2497276a72fd63028e7419abf0fb7ed837baffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before b732db02a2b04cde393638df19de6251ce62a74eaffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before d881d60223aac8fdc12b227d89c76e131e92a9cdaffected · git
- before 3.11not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74295Aug 15, 2026 · ASoC: codecs: hdac_hdmi: Validate written enum value28Monitor
- ← EarlierCVE-2026-74296Aug 15, 2026 · RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one31Monitor
- Later →CVE-2026-74300Aug 15, 2026 · Bluetooth: hci: validate codec capability element length35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 42f3d2c8c18b92ea33e506a38b64f1a8986c2823 | Vendor (CNA) |
| Linux Linux | 4b87a2497276a72fd63028e7419abf0fb7ed837b | Vendor (CNA) |
| Linux Linux | 6fc874fdfb366bfb11c62e6af9a831c8be59ddda | Vendor (CNA) |
| Linux Linux | 9fff54929cc00849d738faa99f06c32399aeb026 | Vendor (CNA) |
| Linux Linux | b732db02a2b04cde393638df19de6251ce62a74e | Vendor (CNA) |
| Linux Linux | b746f949c2ac2b041102836095d6d4a2ef21fa75 | Vendor (CNA) |
| Linux Linux | c1dbf52d24a8cb1aa56780ba51b72e7d495f258c | Vendor (CNA) |
| Linux Linux | d881d60223aac8fdc12b227d89c76e131e92a9cd | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4b87a2497276a72fd63028e7419abf0fb7ed837b
- git.kernel.org/stable/c/6fc874fdfb366bfb11c62e6af9a831c8be59ddda
- git.kernel.org/stable/c/9fff54929cc00849d738faa99f06c32399aeb026
- git.kernel.org/stable/c/b732db02a2b04cde393638df19de6251ce62a74e
- git.kernel.org/stable/c/b746f949c2ac2b041102836095d6d4a2ef21fa75
- git.kernel.org/stable/c/c1dbf52d24a8cb1aa56780ba51b72e7d495f258c
- git.kernel.org/stable/c/d881d60223aac8fdc12b227d89c76e131e92a9cd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.