<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 18:49:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98354</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98354</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/mad: Fix receive buffer leak when PKey enforcement fails&lt;/p&gt;
&lt;p&gt;ib_mad_complete_recv() initializes mad_recv_wc-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Link recv_buf onto rmpp_list right after the list is initialized, so the
error path has something to free.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/mad: Fix receive buffer leak when PKey enforcement fails&lt;/p&gt;
&lt;p&gt;ib_mad_complete_recv() initializes mad_recv_wc-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Link recv_buf onto rmpp_list right after the list is initialized, so the
error path has something to free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98354</guid>
    </item>
    <item>
      <title>GHSA-q823-95hw-ffc6</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-q823-95hw-ffc6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/mad: Fix receive buffer leak when PKey enforcement fails&lt;/p&gt;
&lt;p&gt;ib_mad_complete_recv() initializes mad_recv_wc-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Link recv_buf onto rmpp_list right after the list is initialized, so the
error path has something to free.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/mad: Fix receive buffer leak when PKey enforcement fails&lt;/p&gt;
&lt;p&gt;ib_mad_complete_recv() initializes mad_recv_wc-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Link recv_buf onto rmpp_list right after the list is initialized, so the
error path has something to free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-q823-95hw-ffc6</guid>
    </item>
  </channel>
</rss>
