<?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:55:39 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46035</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46035</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-2026-46035</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — 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-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46035</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46035</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 98 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP On UP kernels (!CONFIG_SMP), spin_trylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, alloc_frozen_pages_nolock() called from NMI context can re-enter rmqueue() and acquire the zone lock that the interrupted context is already holding, corrupting the freelists. With CONFIG_DEBUG_SPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:   BUG: spinlock trylock failure on UP on CPU#0, kunit_try_catch/243   [...]   Call Trace:    &amp;lt;NMI&amp;gt;    dump_stack_lvl+0x3f/0x60    do_raw_spin_trylock+0x41/0x50    _raw_spin_trylock+0x24/0x50    rmqueue.isra.0+0x2a9/0xa70    get_page_from_freelist+0xeb/0x450    alloc_frozen_pages_nolock_noprof+0x111/0x1e0    allocate_slab+0x42a/0x500    ___slab_alloc+0xa7/0x4c0    kmalloc_nolock_noprof+0x164/0x310    [...]    &amp;lt;/NMI&amp;gt; Fix this by returning NULL early when invoked from NMI on a UP kernel.&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 98 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP On UP kernels (!CONFIG_SMP), spin_trylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, alloc_frozen_pages_nolock() called from NMI context can re-enter rmqueue() and acquire the zone lock that the interrupted context is already holding, corrupting the freelists. With CONFIG_DEBUG_SPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:   BUG: spinlock trylock failure on UP on CPU#0, kunit_try_catch/243   [...]   Call Trace:    &amp;lt;NMI&amp;gt;    dump_stack_lvl+0x3f/0x60    do_raw_spin_trylock+0x41/0x50    _raw_spin_trylock+0x24/0x50    rmqueue.isra.0+0x2a9/0xa70    get_page_from_freelist+0xeb/0x450    alloc_frozen_pages_nolock_noprof+0x111/0x1e0    allocate_slab+0x42a/0x500    ___slab_alloc+0xa7/0x4c0    kmalloc_nolock_noprof+0x164/0x310    [...]    &amp;lt;/NMI&amp;gt; Fix this by returning NULL early when invoked from NMI on a UP kernel.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46035</guid>
    </item>
  </channel>
</rss>
