CVE-2026-98354RDMA/mad: Fix receive buffer leak when PKey enforcement fails
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 6, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 47a2b338fe63200d716d2e24131cdb49f17c77da before 4617c9a856188674dddb0ca66979746d07688579; 47a2b338fe63200d716d2e24131cdb49f17c77da builds before 8e2036fb47a5b152d53eadbd35abf311bd34cc7f; from 47a2b338fe63200d716d2e24131cdb49f17c77da before bad289e42f512646a988f278f536d21547df73f1; from 47a2b338fe63200d716d2e24131cdb49f17c77da before 752b30e9d339008e5ce7eed412e9446078916129; 47a2b338fe63200d716d2e24131cdb49f17c77da builds before 39c4ea72a40503e102ae07e6776005f96ca078a6; from 47a2b338fe63200d716d2e24131cdb49f17c77da before 5091e25ec503f7fc02723ca435226467b68caac7; from 47a2b338fe63200d716d2e24131cdb49f17c77da before c0d8df85db146d6275e226cb950023be69dd6c77; from 47a2b338fe63200d716d2e24131cdb49f17c77da before 3476c28c9addfa253f505e6bd87f1f5598b961d0 | CNA record |
References
- https://git.kernel.org/stable/c/4617c9a856188674dddb0ca66979746d07688579
- https://git.kernel.org/stable/c/8e2036fb47a5b152d53eadbd35abf311bd34cc7f
- https://git.kernel.org/stable/c/bad289e42f512646a988f278f536d21547df73f1
- https://git.kernel.org/stable/c/752b30e9d339008e5ce7eed412e9446078916129
- https://git.kernel.org/stable/c/39c4ea72a40503e102ae07e6776005f96ca078a6
- https://git.kernel.org/stable/c/5091e25ec503f7fc02723ca435226467b68caac7
- https://git.kernel.org/stable/c/c0d8df85db146d6275e226cb950023be69dd6c77
- https://git.kernel.org/stable/c/3476c28c9addfa253f505e6bd87f1f5598b961d0
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.