CVE-2026-90435: RDMA/mlx5: Fix integer overflow of user QP buffer 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.12% (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 42fb8aefffff5b458aaa66803364a16e0ea44129, 5b6cfc6d7ff0959dd9766fdc24286a253b59ca77, c845e5e05140ea1bc64a5b1107942d93c876034d.
Low priority for now. Upgrade to Linux Linux 42fb8aefffff5b458aaa66803364a16e0ea44129, 5b6cfc6d7ff0959dd9766fdc24286a253b59ca77, c845e5e05140ea1bc64a5b1107942d93c876034d 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 integer overflow of user QP buffer size set_user_buf_size() computes the QP buffer size by left-shifting the user-supplied rq.wqe_cnt and rq.wqe_shift values as signed integers. A sufficiently large rq.wqe_cnt causes signed integer overflow, which is undefined behavior, and yields a small or negative buf_size, causing ib_umem_get() to map a buffer smaller than the hardware will actually write into. Replace the shifts and addition with check_shl_overflow() and check_add_overflow(), rejecting invalid user inputs. Moreover, guard the identical shift computing qp->sq.offset in _create_user_qp() before set_user_buf_size() is reached.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 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 ccce6b7ef1d7efc59ccba3421e1339c6e63a3d20affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before d99622e40aaa910ade681dfd4dc0fa240a011331affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before c845e5e05140ea1bc64a5b1107942d93c876034daffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 42fb8aefffff5b458aaa66803364a16e0ea44129affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before d7fa2ff72ad1861eac194a4e0075d504ba8c246eaffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before 5b6cfc6d7ff0959dd9766fdc24286a253b59ca77affected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before f917707f0de0832b8ab582391b1f64e549995c6caffected · git
- e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c and later · before dec47e4b0fe34afdf38caa72b4408ba95502e5deaffected · 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-90433Sep 17, 2026 · spi: oc-tiny: switch to managed controller allocation0Monitor
- ← EarlierCVE-2026-90434Sep 17, 2026 · isofs: release zisofs block pointer buffer head0Monitor
- Later →CVE-2026-92476Sep 17, 2026 · crypto: keembay - Initialize completion before requesting IRQ0Monitor
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 | 42fb8aefffff5b458aaa66803364a16e0ea44129 | Vendor (CNA) |
| Linux Linux | 5b6cfc6d7ff0959dd9766fdc24286a253b59ca77 | Vendor (CNA) |
| Linux Linux | c845e5e05140ea1bc64a5b1107942d93c876034d | Vendor (CNA) |
| Linux Linux | ccce6b7ef1d7efc59ccba3421e1339c6e63a3d20 | Vendor (CNA) |
| Linux Linux | d7fa2ff72ad1861eac194a4e0075d504ba8c246e | Vendor (CNA) |
| Linux Linux | d99622e40aaa910ade681dfd4dc0fa240a011331 | Vendor (CNA) |
| Linux Linux | dec47e4b0fe34afdf38caa72b4408ba95502e5de | Vendor (CNA) |
| Linux Linux | f917707f0de0832b8ab582391b1f64e549995c6c | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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).
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 researchersFinders, 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
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5b6cfc6d7ff0959dd9766fdc24286a253b59ca77
- git.kernel.org/stable/c/c845e5e05140ea1bc64a5b1107942d93c876034d
- git.kernel.org/stable/c/ccce6b7ef1d7efc59ccba3421e1339c6e63a3d20
- git.kernel.org/stable/c/d7fa2ff72ad1861eac194a4e0075d504ba8c246e
- git.kernel.org/stable/c/d99622e40aaa910ade681dfd4dc0fa240a011331
- git.kernel.org/stable/c/dec47e4b0fe34afdf38caa72b4408ba95502e5de
- git.kernel.org/stable/c/f917707f0de0832b8ab582391b1f64e549995c6c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.