Service interruption via RDMA MAD receive-buffer leak
Published Oct 6, 2026 · Updated Oct 6, 2026
Memory exhaustion in the RDMA MAD receive path of affected Linux kernels allows remote attackers to disrupt service by repeatedly sending MADs with a wrong PKey. ib_mad_complete_recv() checks the PKey before linking recv_buf to rmpp_list, so its error-path cleanup traverses an empty list and leaves each receive buffer allocated. Exploitation requires a node able to send MADs to an affected RDMA port; repeated failures consume kernel memory rather than directly reading or changing data.
Summary
What happened
Memory exhaustion in the RDMA MAD receive path of affected Linux kernels allows remote attackers to disrupt service by repeatedly sending MADs with a wrong PKey. ib_mad_complete_recv() checks the PKey before linking recv_buf to rmpp_list, so its error-path cleanup traverses an empty list and leaves each receive buffer allocated. Exploitation requires a node able to send MADs to an affected RDMA port; repeated failures consume kernel memory rather than directly reading or changing data.
The record
- CVE
- CVE-2026-98354
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.001
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.13
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <3476c28c9addfa253f505e6bd87f1f5598b961d0
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <39c4ea72a40503e102ae07e6776005f96ca078a6
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <4617c9a856188674dddb0ca66979746d07688579
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <5091e25ec503f7fc02723ca435226467b68caac7
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <752b30e9d339008e5ce7eed412e9446078916129
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <8e2036fb47a5b152d53eadbd35abf311bd34cc7f
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <bad289e42f512646a988f278f536d21547df73f1
- Affected versionversion=47a2b338fe63200d716d2e24131cdb49f17c77da <c0d8df85db146d6275e226cb950023be69dd6c77
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started