<?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:59:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-68262</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-68262</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-68262</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0331 — 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://127.0.0.1:10001/vuln/certfr-2026-avi-0331</link>
      <description>certfr-2026-avi-0331</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0331</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68262</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68262</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 97 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstd_streams (per-CPU contexts) are freed in zstd_exit() during every tfm destruction, rather than being managed at the module level.  When multiple tfms exist, each tfm exit attempts to free the same shared per-CPU streams, resulting in a double-free. This leads to a stack trace similar to:   BUG: Bad page state in process kworker/u16:1  pfn:106fd93   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x106fd93   flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)   page_type: 0xffffffff()   raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000   raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000   page dumped because: nonzero entire_mapcount   Modules linked in: ...   CPU: 3 UID: 0 PID: 2506 Comm: kworker/u16:1 Kdump: loaded Tainted: G    B   Hardware name: ...   Workqueue: btrfs-delalloc btrfs_work_helper   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x5d/0x80    bad_page+0x71/0xd0    free_unref_page_prepare+0x24e/0x490    free_unref_page+0x60/0x170    crypto_acomp_free_streams+0x5d/0xc0    crypto_acomp_exit_tfm+0x23/0x50    crypto_destroy_tfm+0x60/0xc0    ... Change the lifecycle management of zstd_streams to free the streams only once during module cleanup.&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 97 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstd_streams (per-CPU contexts) are freed in zstd_exit() during every tfm destruction, rather than being managed at the module level.  When multiple tfms exist, each tfm exit attempts to free the same shared per-CPU streams, resulting in a double-free. This leads to a stack trace similar to:   BUG: Bad page state in process kworker/u16:1  pfn:106fd93   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x106fd93   flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)   page_type: 0xffffffff()   raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000   raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000   page dumped because: nonzero entire_mapcount   Modules linked in: ...   CPU: 3 UID: 0 PID: 2506 Comm: kworker/u16:1 Kdump: loaded Tainted: G    B   Hardware name: ...   Workqueue: btrfs-delalloc btrfs_work_helper   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x5d/0x80    bad_page+0x71/0xd0    free_unref_page_prepare+0x24e/0x490    free_unref_page+0x60/0x170    crypto_acomp_free_streams+0x5d/0xc0    crypto_acomp_exit_tfm+0x23/0x50    crypto_destroy_tfm+0x60/0xc0    ... Change the lifecycle management of zstd_streams to free the streams only once during module cleanup.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68262</guid>
    </item>
  </channel>
</rss>
