<?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>Fri, 20 Nov 2026 21:27:30 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99522</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99522</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/irdma: avoid use-after-free in icrdma_remove&lt;/p&gt;
&lt;p&gt;icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():&lt;/p&gt;
&lt;p&gt;irdma_ib_unregister_device(iwdev)
    -&amp;gt; ib_unregister_device(&amp;amp;iwdev-&amp;gt;ibdev)
      -&amp;gt; __ib_unregister_device()
        -&amp;gt; ib_dealloc_device()&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;However, icrdma_remove() currently accesses iwdev-&amp;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.&lt;/p&gt;
&lt;p&gt;Save iwdev-&amp;gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&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/irdma: avoid use-after-free in icrdma_remove&lt;/p&gt;
&lt;p&gt;icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():&lt;/p&gt;
&lt;p&gt;irdma_ib_unregister_device(iwdev)
    -&amp;gt; ib_unregister_device(&amp;amp;iwdev-&amp;gt;ibdev)
      -&amp;gt; __ib_unregister_device()
        -&amp;gt; ib_dealloc_device()&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;However, icrdma_remove() currently accesses iwdev-&amp;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.&lt;/p&gt;
&lt;p&gt;Save iwdev-&amp;gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99522</guid>
    </item>
    <item>
      <title>GHSA-gfx7-j6q8-pv78</title>
      <link>https://db.gcve.eu/vuln/ghsa-gfx7-j6q8-pv78</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/irdma: avoid use-after-free in icrdma_remove&lt;/p&gt;
&lt;p&gt;icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():&lt;/p&gt;
&lt;p&gt;irdma_ib_unregister_device(iwdev)
    -&amp;gt; ib_unregister_device(&amp;amp;iwdev-&amp;gt;ibdev)
      -&amp;gt; __ib_unregister_device()
        -&amp;gt; ib_dealloc_device()&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;However, icrdma_remove() currently accesses iwdev-&amp;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.&lt;/p&gt;
&lt;p&gt;Save iwdev-&amp;gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&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/irdma: avoid use-after-free in icrdma_remove&lt;/p&gt;
&lt;p&gt;icrdma_remove() dereferences iwdev after calling
irdma_ib_unregister_device():&lt;/p&gt;
&lt;p&gt;irdma_ib_unregister_device(iwdev)
    -&amp;gt; ib_unregister_device(&amp;amp;iwdev-&amp;gt;ibdev)
      -&amp;gt; __ib_unregister_device()
        -&amp;gt; ib_dealloc_device()&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;However, icrdma_remove() currently accesses iwdev-&amp;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.&lt;/p&gt;
&lt;p&gt;Save iwdev-&amp;gt;rf before unregistering the RDMA device and use the saved
pointer for the remaining cleanup.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gfx7-j6q8-pv78</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;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&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
