CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure
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 2982eaf3b9d2d953318c74cd6f1b7576ea6d7b1f, 32d2cdb0f3cac430b04124c3b7248851fe2037f8, 5a1a7a5e2fe1a15824fa9ae5edd8f008259471d1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 2982eaf3b9d2d953318c74cd6f1b7576ea6d7b1f, 32d2cdb0f3cac430b04124c3b7248851fe2037f8, 5a1a7a5e2fe1a15824fa9ae5edd8f008259471d1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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/rvt: Return NULL after port allocation failure rvt_alloc_device() deallocates the IB device when its port array cannot be allocated but then returns the pointer to the released allocation. Callers treat any non-NULL value as valid and dereference it, resulting in a use-after-free. Return NULL immediately after deallocation so callers can propagate the allocation failure.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
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.
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
- 4.6affected
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before 32d2cdb0f3cac430b04124c3b7248851fe2037f8affected · git
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before b7129930d1ec46c03a0de07fdce6c29f75795006affected · git
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before 5a1a7a5e2fe1a15824fa9ae5edd8f008259471d1affected · git
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before 80968b42d13080bf7bc1f3ee17fef126ce2ad98faffected · git
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before b1e1b25723af44328524c7b54433e4bf0ab9930caffected · git
- ff6acd69518e0a84bd9c9b7f1bd4313f7076db97 and later · before 2982eaf3b9d2d953318c74cd6f1b7576ea6d7b1faffected · git
- before 4.6not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| 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-93102Sep 17, 2026 · RDMA/hfi1: Free RX data on late probe failure0Monitor
- ← EarlierCVE-2026-93103Sep 17, 2026 · RDMA/hfi1: Preserve unit 0 on allocation failure0Monitor
- Later →CVE-2026-93105Sep 17, 2026 · esp: do not unref managed frag pages in esp_ssg_unref()31Monitor
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 | 2982eaf3b9d2d953318c74cd6f1b7576ea6d7b1f | Vendor (CNA) |
| Linux Linux | 32d2cdb0f3cac430b04124c3b7248851fe2037f8 | Vendor (CNA) |
| Linux Linux | 5a1a7a5e2fe1a15824fa9ae5edd8f008259471d1 | Vendor (CNA) |
| Linux Linux | 80968b42d13080bf7bc1f3ee17fef126ce2ad98f | Vendor (CNA) |
| Linux Linux | b1e1b25723af44328524c7b54433e4bf0ab9930c | Vendor (CNA) |
| Linux Linux | b7129930d1ec46c03a0de07fdce6c29f75795006 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | 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
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/32d2cdb0f3cac430b04124c3b7248851fe2037f8
- git.kernel.org/stable/c/5a1a7a5e2fe1a15824fa9ae5edd8f008259471d1
- git.kernel.org/stable/c/80968b42d13080bf7bc1f3ee17fef126ce2ad98f
- git.kernel.org/stable/c/b1e1b25723af44328524c7b54433e4bf0ab9930c
- git.kernel.org/stable/c/b7129930d1ec46c03a0de07fdce6c29f75795006
Vendor advisories and official records. Exploit/PoC links are deliberately left out.