CVE-2026-98354 — RDMA/mad: Fix receive buffer leak when PKey enforcement fails
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 4617c9a856188674dddb0ca66979746d07688579≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 8e2036fb47a5b152d53eadbd35abf311bd34cc7f≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < bad289e42f512646a988f278f536d21547df73f1≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 752b30e9d339008e5ce7eed412e9446078916129≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 39c4ea72a40503e102ae07e6776005f96ca078a6≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 5091e25ec503f7fc02723ca435226467b68caac7≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < c0d8df85db146d6275e226cb950023be69dd6c77≥ 47a2b338fe63200d716d2e24131cdb49f17c77da and < 3476c28c9addfa253f505e6bd87f1f5598b961d0 and 1 moreversion 4.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/c0d8df85db146d6275e226cb950023be69dd6c77
- git.kernel.org/stable/c/4617c9a856188674dddb0ca66979746d07688579
- git.kernel.org/stable/c/752b30e9d339008e5ce7eed412e9446078916129
- git.kernel.org/stable/c/8e2036fb47a5b152d53eadbd35abf311bd34cc7f
- git.kernel.org/stable/c/3476c28c9addfa253f505e6bd87f1f5598b961d0
- git.kernel.org/stable/c/bad289e42f512646a988f278f536d21547df73f1
- git.kernel.org/stable/c/39c4ea72a40503e102ae07e6776005f96ca078a6
- git.kernel.org/stable/c/5091e25ec503f7fc02723ca435226467b68caac7
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 14h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 14h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98354 is "RDMA/mad: Fix receive buffer leak when PKey enforcement fails", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.