<?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:35 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99453</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99453</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xen-blkfront: unbind irq before tearing down ring and shadow requests&lt;/p&gt;
&lt;p&gt;In blkif_free_ring(), the driver tears down the ring&amp;#39;s persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.&lt;/p&gt;
&lt;p&gt;While blkif_free_ring() is freeing persistent grants and clearing the
shadow array, the event channel interrupt (blkif_interrupt) is still
registered and active.  If an interrupt arrives from the backend during
this teardown window, blkif_interrupt() reads rinfo-&amp;gt;ring.sring and,
via blkif_completion(), accesses rinfo-&amp;gt;shadow[id].grants_used and
rinfo-&amp;gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&amp;gt;ring_lock, and the handler only checks
info-&amp;gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by moving unbind_from_irqhandler() to the beginning of
blkif_free_ring().  Calling unbind_from_irqhandler() first frees the
IRQ and synchronizes with any in-flight interrupt handlers on other CPUs
before ring memory and shadow request structures are deallocated,
matching the teardown order in drivers/net/xen-netfront.c.&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;xen-blkfront: unbind irq before tearing down ring and shadow requests&lt;/p&gt;
&lt;p&gt;In blkif_free_ring(), the driver tears down the ring&amp;#39;s persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.&lt;/p&gt;
&lt;p&gt;While blkif_free_ring() is freeing persistent grants and clearing the
shadow array, the event channel interrupt (blkif_interrupt) is still
registered and active.  If an interrupt arrives from the backend during
this teardown window, blkif_interrupt() reads rinfo-&amp;gt;ring.sring and,
via blkif_completion(), accesses rinfo-&amp;gt;shadow[id].grants_used and
rinfo-&amp;gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&amp;gt;ring_lock, and the handler only checks
info-&amp;gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by moving unbind_from_irqhandler() to the beginning of
blkif_free_ring().  Calling unbind_from_irqhandler() first frees the
IRQ and synchronizes with any in-flight interrupt handlers on other CPUs
before ring memory and shadow request structures are deallocated,
matching the teardown order in drivers/net/xen-netfront.c.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99453</guid>
    </item>
    <item>
      <title>GHSA-v8p2-px2j-h8f2</title>
      <link>https://db.gcve.eu/vuln/ghsa-v8p2-px2j-h8f2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xen-blkfront: unbind irq before tearing down ring and shadow requests&lt;/p&gt;
&lt;p&gt;In blkif_free_ring(), the driver tears down the ring&amp;#39;s persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.&lt;/p&gt;
&lt;p&gt;While blkif_free_ring() is freeing persistent grants and clearing the
shadow array, the event channel interrupt (blkif_interrupt) is still
registered and active.  If an interrupt arrives from the backend during
this teardown window, blkif_interrupt() reads rinfo-&amp;gt;ring.sring and,
via blkif_completion(), accesses rinfo-&amp;gt;shadow[id].grants_used and
rinfo-&amp;gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&amp;gt;ring_lock, and the handler only checks
info-&amp;gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by moving unbind_from_irqhandler() to the beginning of
blkif_free_ring().  Calling unbind_from_irqhandler() first frees the
IRQ and synchronizes with any in-flight interrupt handlers on other CPUs
before ring memory and shadow request structures are deallocated,
matching the teardown order in drivers/net/xen-netfront.c.&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;xen-blkfront: unbind irq before tearing down ring and shadow requests&lt;/p&gt;
&lt;p&gt;In blkif_free_ring(), the driver tears down the ring&amp;#39;s persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.&lt;/p&gt;
&lt;p&gt;While blkif_free_ring() is freeing persistent grants and clearing the
shadow array, the event channel interrupt (blkif_interrupt) is still
registered and active.  If an interrupt arrives from the backend during
this teardown window, blkif_interrupt() reads rinfo-&amp;gt;ring.sring and,
via blkif_completion(), accesses rinfo-&amp;gt;shadow[id].grants_used and
rinfo-&amp;gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&amp;gt;ring_lock, and the handler only checks
info-&amp;gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;Fix this by moving unbind_from_irqhandler() to the beginning of
blkif_free_ring().  Calling unbind_from_irqhandler() first frees the
IRQ and synchronizes with any in-flight interrupt handlers on other CPUs
before ring memory and shadow request structures are deallocated,
matching the teardown order in drivers/net/xen-netfront.c.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-v8p2-px2j-h8f2</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>
