CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 3476c28c9addfa253f505e6bd87f1f5598b961d0, 39c4ea72a40503e102ae07e6776005f96ca078a6, 4617c9a856188674dddb0ca66979746d07688579; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 3476c28c9addfa253f505e6bd87f1f5598b961d0, 39c4ea72a40503e102ae07e6776005f96ca078a6, 4617c9a856188674dddb0ca66979746d07688579; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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/mad: Fix receive buffer leak when PKey enforcement fails ib_mad_complete_recv() initializes mad_recv_wc->rmpp_list and then runs ib_mad_enforce_security() before linking recv_buf onto that list. On failure it calls ib_free_recv_mad(), which only walks rmpp_list and frees the ib_mad_private of every buffer found there. As the list is still empty at that point, nothing is freed at all. The caller cannot clean up either: ib_mad_recv_done() sets recv to NULL right after ib_mad_complete_recv() returns, assuming the MAD layer took ownership of the buffer. Every MAD that fails the PKey check therefore leaks one ib_mad_private (about 300 bytes per IB port MAD, ~2K for OPA), and a remote node can trigger this repeatedly by sending MADs with a wrong PKey. Link recv_buf onto rmpp_list right after the list is initialized, so the error path has something to free.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
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.
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
- 4.13affected
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 4617c9a856188674dddb0ca66979746d07688579affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 8e2036fb47a5b152d53eadbd35abf311bd34cc7faffected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before bad289e42f512646a988f278f536d21547df73f1affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 752b30e9d339008e5ce7eed412e9446078916129affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 39c4ea72a40503e102ae07e6776005f96ca078a6affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 5091e25ec503f7fc02723ca435226467b68caac7affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before c0d8df85db146d6275e226cb950023be69dd6c77affected · git
- 47a2b338fe63200d716d2e24131cdb49f17c77da and later · before 3476c28c9addfa253f505e6bd87f1f5598b961d0affected · git
- before 4.13not 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.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-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-98352Oct 6, 2026 · RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted0Monitor
- ← EarlierCVE-2026-98353Oct 6, 2026 · RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables0Monitor
- Later →CVE-2026-98355Oct 6, 2026 · RDMA/rtrs: guard against null kobj name0Monitor
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 | 3476c28c9addfa253f505e6bd87f1f5598b961d0 | Vendor (CNA) |
| Linux Linux | 39c4ea72a40503e102ae07e6776005f96ca078a6 | Vendor (CNA) |
| Linux Linux | 4617c9a856188674dddb0ca66979746d07688579 | Vendor (CNA) |
| Linux Linux | 5091e25ec503f7fc02723ca435226467b68caac7 | Vendor (CNA) |
| Linux Linux | 752b30e9d339008e5ce7eed412e9446078916129 | Vendor (CNA) |
| Linux Linux | 8e2036fb47a5b152d53eadbd35abf311bd34cc7f | Vendor (CNA) |
| Linux Linux | bad289e42f512646a988f278f536d21547df73f1 | Vendor (CNA) |
| Linux Linux | c0d8df85db146d6275e226cb950023be69dd6c77 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+38 d
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
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 (2)
- Exploit maturity— → 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/39c4ea72a40503e102ae07e6776005f96ca078a6
- git.kernel.org/stable/c/4617c9a856188674dddb0ca66979746d07688579
- git.kernel.org/stable/c/5091e25ec503f7fc02723ca435226467b68caac7
- git.kernel.org/stable/c/752b30e9d339008e5ce7eed412e9446078916129
- git.kernel.org/stable/c/8e2036fb47a5b152d53eadbd35abf311bd34cc7f
- git.kernel.org/stable/c/bad289e42f512646a988f278f536d21547df73f1
- git.kernel.org/stable/c/c0d8df85db146d6275e226cb950023be69dd6c77
Vendor advisories and official records. Exploit/PoC links are deliberately left out.