<?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-11-20T21:27:29.794277+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/fkie_cve-2026-99522</id>
    <title>fkie_cve-2026-99522</title>
    <updated>2026-11-20T21:27:29.797474+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>RDMA/irdma: avoid use-after-free in icrdma_remove</p>
<p>icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():</p>
<p>irdma_ib_unregister_device(iwdev)
    -&gt; ib_unregister_device(&amp;iwdev-&gt;ibdev)
      -&gt; __ib_unregister_device()
        -&gt; ib_dealloc_device()</p>
<p>irdma registers irdma_ib_dealloc_device() as the dealloc_driver
callback in its ib_device_ops. The RDMA core explicitly documents
ib_unregister_device() that when ops.dealloc_driver is used, ib_dev
will be freed upon return from the function.</p>
<p>The ib_device is embedded in struct irdma_device and iwdev itself was
allocated by ib_alloc_device(irdma_device, ibdev). Consequently, once
irdma_ib_unregister_device() returns, iwdev must no longer be
dereferenced.</p>
<p>However, icrdma_remove() currently accesses iwdev-&gt;rf afterwards when
deinitializing interrupts, destroying ah_tbl_lock, and freeing rf.
Although the final ib_device storage is released with kfree_rcu(), the
object lifetime has already ended and callers must not rely on the RCU
grace period to continue dereferencing iwdev.</p>
<p>Save iwdev-&gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.</p>
<p>This issue was found by manual code inspection.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99522"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-gfx7-j6q8-pv78</id>
    <title>GHSA-gfx7-j6q8-pv78</title>
    <updated>2026-11-20T21:27:29.797560+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>RDMA/irdma: avoid use-after-free in icrdma_remove</p>
<p>icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():</p>
<p>irdma_ib_unregister_device(iwdev)
    -&gt; ib_unregister_device(&amp;iwdev-&gt;ibdev)
      -&gt; __ib_unregister_device()
        -&gt; ib_dealloc_device()</p>
<p>irdma registers irdma_ib_dealloc_device() as the dealloc_driver
callback in its ib_device_ops. The RDMA core explicitly documents
ib_unregister_device() that when ops.dealloc_driver is used, ib_dev
will be freed upon return from the function.</p>
<p>The ib_device is embedded in struct irdma_device and iwdev itself was
allocated by ib_alloc_device(irdma_device, ibdev). Consequently, once
irdma_ib_unregister_device() returns, iwdev must no longer be
dereferenced.</p>
<p>However, icrdma_remove() currently accesses iwdev-&gt;rf afterwards when
deinitializing interrupts, destroying ah_tbl_lock, and freeing rf.
Although the final ib_device storage is released with kfree_rcu(), the
object lifetime has already ended and callers must not rely on the RCU
grace period to continue dereferencing iwdev.</p>
<p>Save iwdev-&gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.</p>
<p>This issue was found by manual code inspection.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-gfx7-j6q8-pv78"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:27:29.797594+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
