<?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://cve.radiocsirt.org</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>Thu, 08 Oct 2026 04:37:26 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-63951 — CVE-2026-63951 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-63951</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-63951</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-348321</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348321</link>
      <description>EUVD-2026-348321</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348321</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63951</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63951</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;zram: fix use-after-free in zram_writeback_endio&lt;/p&gt;
&lt;p&gt;A crash was observed in zram_writeback_endio due to a NULL pointer
dereference in wake_up.  The root cause is a race condition between the
bio completion handler (zram_writeback_endio) and the writeback task.&lt;/p&gt;
&lt;p&gt;In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after
releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the
writeback task can see num_inflight become 0, return, and free wb_ctl
before zram_writeback_endio calls wake_up().&lt;/p&gt;
&lt;p&gt;CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store)
============================     ============================
                                 zram_writeback_slots
                                   zram_submit_wb_request
                                   zram_submit_wb_request
                                   wait_event(wb_ctl-&amp;gt;done_wait)
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);
                                   zram_complete_done_reqs
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                   while (num_inflight) &amp;gt; 0)
                                     spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                     list_del(&amp;amp;req-&amp;gt;entry);
                                     spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&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;zram: fix use-after-free in zram_writeback_endio&lt;/p&gt;
&lt;p&gt;A crash was observed in zram_writeback_endio due to a NULL pointer
dereference in wake_up.  The root cause is a race condition between the
bio completion handler (zram_writeback_endio) and the writeback task.&lt;/p&gt;
&lt;p&gt;In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after
releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the
writeback task can see num_inflight become 0, return, and free wb_ctl
before zram_writeback_endio calls wake_up().&lt;/p&gt;
&lt;p&gt;CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store)
============================     ============================
                                 zram_writeback_slots
                                   zram_submit_wb_request
                                   zram_submit_wb_request
                                   wait_event(wb_ctl-&amp;gt;done_wait)
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);
                                   zram_complete_done_reqs
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                   while (num_inflight) &amp;gt; 0)
                                     spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                     list_del(&amp;amp;req-&amp;gt;entry);
                                     spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-63951</guid>
    </item>
    <item>
      <title>GHSA-jmwm-428x-w863</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jmwm-428x-w863</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;zram: fix use-after-free in zram_writeback_endio&lt;/p&gt;
&lt;p&gt;A crash was observed in zram_writeback_endio due to a NULL pointer
dereference in wake_up.  The root cause is a race condition between the
bio completion handler (zram_writeback_endio) and the writeback task.&lt;/p&gt;
&lt;p&gt;In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after
releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the
writeback task can see num_inflight become 0, return, and free wb_ctl
before zram_writeback_endio calls wake_up().&lt;/p&gt;
&lt;p&gt;CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store)
============================     ============================
                                 zram_writeback_slots
                                   zram_submit_wb_request
                                   zram_submit_wb_request
                                   wait_event(wb_ctl-&amp;gt;done_wait)
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);
                                   zram_complete_done_reqs
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                   while (num_inflight) &amp;gt; 0)
                                     spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                     list_del(&amp;amp;req-&amp;gt;entry);
                                     spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&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;zram: fix use-after-free in zram_writeback_endio&lt;/p&gt;
&lt;p&gt;A crash was observed in zram_writeback_endio due to a NULL pointer
dereference in wake_up.  The root cause is a race condition between the
bio completion handler (zram_writeback_endio) and the writeback task.&lt;/p&gt;
&lt;p&gt;In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after
releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the
writeback task can see num_inflight become 0, return, and free wb_ctl
before zram_writeback_endio calls wake_up().&lt;/p&gt;
&lt;p&gt;CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store)
============================     ============================
                                 zram_writeback_slots
                                   zram_submit_wb_request
                                   zram_submit_wb_request
                                   wait_event(wb_ctl-&amp;gt;done_wait)
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);
                                   zram_complete_done_reqs
spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs);
spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                   while (num_inflight) &amp;gt; 0)
                                     spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);
                                     list_del(&amp;amp;req-&amp;gt;entry);
                                     spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jmwm-428x-w863</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63951</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63951</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zram_writeback_endio A crash was observed in zram_writeback_endio due to a NULL pointer dereference in wake_up.  The root cause is a race condition between the bio completion handler (zram_writeback_endio) and the writeback task. In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the writeback task can see num_inflight become 0, return, and free wb_ctl before zram_writeback_endio calls wake_up(). CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store) ============================     ============================                                  zram_writeback_slots                                    zram_submit_wb_request                                    zram_submit_wb_request                                    wait_event(wb_ctl-&amp;gt;done_wait) spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock); list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs); spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock); wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);                                    zram_complete_done_reqs spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock); list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs); spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);                                    while (num_inflight) &amp;gt; 0)                                      spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);                                      list_del(&amp;amp;req-&amp;gt;entry);                                      spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zram_writeback_endio A crash was observed in zram_writeback_endio due to a NULL pointer dereference in wake_up.  The root cause is a race condition between the bio completion handler (zram_writeback_endio) and the writeback task. In zram_writeback_endio, wake_up() is called on &amp;amp;wb_ctl-&amp;gt;done_wait after releasing wb_ctl-&amp;gt;done_lock.  This creates a race window where the writeback task can see num_inflight become 0, return, and free wb_ctl before zram_writeback_endio calls wake_up(). CPU 0 (zram_writeback_endio)     CPU 1 (writeback_store) ============================     ============================                                  zram_writeback_slots                                    zram_submit_wb_request                                    zram_submit_wb_request                                    wait_event(wb_ctl-&amp;gt;done_wait) spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock); list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs); spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock); wake_up(&amp;amp;wb_ctl-&amp;gt;done_wait);                                    zram_complete_done_reqs spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock); list_add(&amp;amp;req-&amp;gt;entry, &amp;amp;wb_ctl-&amp;gt;done_reqs); spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);                                    while (num_inflight) &amp;gt; 0)                                      spin_lock(&amp;amp;wb_ctl-&amp;gt;done_lock);                                      list_del(&amp;amp;req-&amp;gt;entry);                                      spin_unlock(&amp;amp;wb_ctl-&amp;gt;done_lock);…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63951</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
