<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 05:51:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64424</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64424</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-64424</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1031 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1031</link>
      <description>certfr-2026-avi-1031</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1031</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64424</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64424</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netpoll: fix a use-after-free on shutdown path There is a use-after-free error on netpoll, which is clearly detected by KASAN.       BUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0x3b/0x80       Read of size 1 at addr ... by task kworker/9:1       Workqueue: events queue_process       Call Trace:        skb_dequeue+0x1e/0xb0        queue_process+0x2c/0x600        process_scheduled_works+0x4b6/0x850        worker_thread+0x414/0x5a0       Allocated by task 242:        __netpoll_setup+0x201/0x4a0        netpoll_setup+0x249/0x550        enabled_store+0x32f/0x380       Freed by task 0:        kfree+0x1b7/0x540        rcu_core+0x3f8/0x7a0 The problem happens when there is a pending TX worker running in parallel with the cleanup path. This is what happens on netpoll shutdown path: 1) __netpoll_cleanup() is called 2) set dev-&amp;gt;npinfo to NULL 3) call_rcu() with rcu_cleanup_netpoll_info()   3.1) rcu_cleanup_netpoll_info() tries to cancel all workers with        cancel_delayed_work(), but doesn&amp;#39;t wait for the worker to finish 4) and kfree(npinfo); Because 3.1) doesn&amp;#39;t really cancel the work, as the comment says &amp;#34;we can&amp;#39;t call cancel_delayed_work_sync here, as we are in softirq&amp;#34;, the TX worker can run after 4). Tl;DR: queue_process() is not an RCU reader, it reaches npinfo through the work item via container_of(). Use disable_delayed_work_sync() to ensure the worker is completely stopped and prevent any futur…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netpoll: fix a use-after-free on shutdown path There is a use-after-free error on netpoll, which is clearly detected by KASAN.       BUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0x3b/0x80       Read of size 1 at addr ... by task kworker/9:1       Workqueue: events queue_process       Call Trace:        skb_dequeue+0x1e/0xb0        queue_process+0x2c/0x600        process_scheduled_works+0x4b6/0x850        worker_thread+0x414/0x5a0       Allocated by task 242:        __netpoll_setup+0x201/0x4a0        netpoll_setup+0x249/0x550        enabled_store+0x32f/0x380       Freed by task 0:        kfree+0x1b7/0x540        rcu_core+0x3f8/0x7a0 The problem happens when there is a pending TX worker running in parallel with the cleanup path. This is what happens on netpoll shutdown path: 1) __netpoll_cleanup() is called 2) set dev-&amp;gt;npinfo to NULL 3) call_rcu() with rcu_cleanup_netpoll_info()   3.1) rcu_cleanup_netpoll_info() tries to cancel all workers with        cancel_delayed_work(), but doesn&amp;#39;t wait for the worker to finish 4) and kfree(npinfo); Because 3.1) doesn&amp;#39;t really cancel the work, as the comment says &amp;#34;we can&amp;#39;t call cancel_delayed_work_sync here, as we are in softirq&amp;#34;, the TX worker can run after 4). Tl;DR: queue_process() is not an RCU reader, it reaches npinfo through the work item via container_of(). Use disable_delayed_work_sync() to ensure the worker is completely stopped and prevent any futur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64424</guid>
    </item>
  </channel>
</rss>
