<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T21:15:55.139811+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-90423</id>
    <title>CVE-2026-90423 — RDMA/rxe: Fix UAF in ODP init error-handling path</title>
    <updated>2026-09-30T21:15:55.141157+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>RDMA/rxe: Fix UAF in ODP init error-handling path</p>
<p>rxe_odp_mr_init_user() stores &amp;umem_odp-&gt;umem in mr-&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.</p>
<p>rxe_reg_user_mr() then unwinds the error through rxe_cleanup(),
rxe_mr_cleanup(), ib_umem_release(mr-&gt;umem). There is an
IS_ERR_OR_NULL(umem) check at the start of ib_umem_release().
But since mr-&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-&gt;is_dmabuf, causing UAF.</p>
<p>Fix the UAF by clearing mr-&gt;umem after releasing the failed
ODP umem so the MR cleanup path does not release it again.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-90423"/>
  </entry>
</feed>
