<?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://db.gcve.eu</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>Wed, 30 Sep 2026 21:17:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90423 — RDMA/rxe: Fix UAF in ODP init error-handling path</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90423</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix UAF in ODP init error-handling path&lt;/p&gt;
&lt;p&gt;rxe_odp_mr_init_user() stores &amp;amp;umem_odp-&amp;gt;umem in mr-&amp;gt;umem before
calling rxe_odp_init_pages(). If rxe_odp_init_pages() fails,
rxe_odp_mr_init_user() releases umem_odp and returns an error.&lt;/p&gt;
&lt;p&gt;rxe_reg_user_mr() then unwinds the error through rxe_cleanup(),
rxe_mr_cleanup(), ib_umem_release(mr-&amp;gt;umem). There is an
IS_ERR_OR_NULL(umem) check at the start of ib_umem_release().
But since mr-&amp;gt;umem is NOT reset to NULL in the error handling
path of rxe_odp_mr_init_user(), the check passes and it reads
already-freed fields like umem-&amp;gt;is_dmabuf, causing UAF.&lt;/p&gt;
&lt;p&gt;Fix the UAF by clearing mr-&amp;gt;umem after releasing the failed
ODP umem so the MR cleanup path does not release it again.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix UAF in ODP init error-handling path&lt;/p&gt;
&lt;p&gt;rxe_odp_mr_init_user() stores &amp;amp;umem_odp-&amp;gt;umem in mr-&amp;gt;umem before
calling rxe_odp_init_pages(). If rxe_odp_init_pages() fails,
rxe_odp_mr_init_user() releases umem_odp and returns an error.&lt;/p&gt;
&lt;p&gt;rxe_reg_user_mr() then unwinds the error through rxe_cleanup(),
rxe_mr_cleanup(), ib_umem_release(mr-&amp;gt;umem). There is an
IS_ERR_OR_NULL(umem) check at the start of ib_umem_release().
But since mr-&amp;gt;umem is NOT reset to NULL in the error handling
path of rxe_odp_mr_init_user(), the check passes and it reads
already-freed fields like umem-&amp;gt;is_dmabuf, causing UAF.&lt;/p&gt;
&lt;p&gt;Fix the UAF by clearing mr-&amp;gt;umem after releasing the failed
ODP umem so the MR cleanup path does not release it again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90423</guid>
    </item>
  </channel>
</rss>
