Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98354RDMA/mad: Fix receive buffer leak when PKey enforcement fails

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 4617c9a856188674dddb0ca66979746d07688579
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 8e2036fb47a5b152d53eadbd35abf311bd34cc7f
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < bad289e42f512646a988f278f536d21547df73f1
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 752b30e9d339008e5ce7eed412e9446078916129
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 39c4ea72a40503e102ae07e6776005f96ca078a6
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 5091e25ec503f7fc02723ca435226467b68caac7
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < c0d8df85db146d6275e226cb950023be69dd6c77
    • affected 47a2b338fe63200d716d2e24131cdb49f17c77da – < 3476c28c9addfa253f505e6bd87f1f5598b961d0
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98354 badge
[![CVE-2026-98354](https://cveledger.app/badge/CVE-2026-98354.svg)](https://cveledger.app/cve/CVE-2026-98354)

Record last updated .