<?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:35.349121+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-99453</id>
    <title>fkie_cve-2026-99453</title>
    <updated>2026-11-20T21:27:35.354367+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>xen-blkfront: unbind irq before tearing down ring and shadow requests</p>
<p>In blkif_free_ring(), the driver tears down the ring's persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.</p>
<p>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-&gt;ring.sring and,
via blkif_completion(), accesses rinfo-&gt;shadow[id].grants_used and
rinfo-&gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&gt;ring_lock, and the handler only checks
info-&gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99453"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-v8p2-px2j-h8f2</id>
    <title>GHSA-v8p2-px2j-h8f2</title>
    <updated>2026-11-20T21:27:35.354524+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>xen-blkfront: unbind irq before tearing down ring and shadow requests</p>
<p>In blkif_free_ring(), the driver tears down the ring's persistent grants,
shadow request arrays, and shared ring structure (xenbus_teardown_ring),
and only calls unbind_from_irqhandler() at the very end.</p>
<p>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-&gt;ring.sring and,
via blkif_completion(), accesses rinfo-&gt;shadow[id].grants_used and
rinfo-&gt;shadow[id].sg.  blkif_free_ring() tears these structures down
without holding rinfo-&gt;ring_lock, and the handler only checks
info-&gt;connected at entry, so this is a real race resulting in a
use-after-free or NULL pointer dereference.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-v8p2-px2j-h8f2"/>
  </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:35.354595+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>
