<?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 03:40:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26987</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26987</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-2024-26987</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</link>
      <description>certfr-2024-avi-0381</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26987</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26987</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 84 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix deadlock when hugetlb_optimize_vmemmap is enabled When I did hard offline test with hugetlb pages, below deadlock occurs: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-11409-gf6cef5f8c37f #1 Not tainted ------------------------------------------------------ bash/46904 is trying to acquire lock: ffffffffabe68910 (cpu_hotplug_lock){++++}-{0:0}, at: static_key_slow_dec+0x16/0x60 but task is already holding lock: ffffffffabf92ea8 (pcp_batch_high_lock){+.+.}-{3:3}, at: zone_pcp_disable+0x16/0x40 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -&amp;gt; #1 (pcp_batch_high_lock){+.+.}-{3:3}:        __mutex_lock+0x6c/0x770        page_alloc_cpu_online+0x3c/0x70        cpuhp_invoke_callback+0x397/0x5f0        __cpuhp_invoke_callback_range+0x71/0xe0        _cpu_up+0xeb/0x210        cpu_up+0x91/0xe0        cpuhp_bringup_mask+0x49/0xb0        bringup_nonboot_cpus+0xb7/0xe0        smp_init+0x25/0xa0        kernel_init_freeable+0x15f/0x3e0        kernel_init+0x15/0x1b0        ret_from_fork+0x2f/0x50        ret_from_fork_asm+0x1a/0x30 -&amp;gt; #0 (cpu_hotplug_lock){++++}-{0:0}:        __lock_acquire+0x1298/0x1cd0        lock_acquire+0xc0/0x2b0        cpus_read_lock+0x2a/0xc0        static_key_slow_dec+0x16/0x60        __hugetlb_vmemmap_restore_folio+0x1b9/0x200        dissolve_free_huge_page+0x21…&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 84 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix deadlock when hugetlb_optimize_vmemmap is enabled When I did hard offline test with hugetlb pages, below deadlock occurs: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-11409-gf6cef5f8c37f #1 Not tainted ------------------------------------------------------ bash/46904 is trying to acquire lock: ffffffffabe68910 (cpu_hotplug_lock){++++}-{0:0}, at: static_key_slow_dec+0x16/0x60 but task is already holding lock: ffffffffabf92ea8 (pcp_batch_high_lock){+.+.}-{3:3}, at: zone_pcp_disable+0x16/0x40 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -&amp;gt; #1 (pcp_batch_high_lock){+.+.}-{3:3}:        __mutex_lock+0x6c/0x770        page_alloc_cpu_online+0x3c/0x70        cpuhp_invoke_callback+0x397/0x5f0        __cpuhp_invoke_callback_range+0x71/0xe0        _cpu_up+0xeb/0x210        cpu_up+0x91/0xe0        cpuhp_bringup_mask+0x49/0xb0        bringup_nonboot_cpus+0xb7/0xe0        smp_init+0x25/0xa0        kernel_init_freeable+0x15f/0x3e0        kernel_init+0x15/0x1b0        ret_from_fork+0x2f/0x50        ret_from_fork_asm+0x1a/0x30 -&amp;gt; #0 (cpu_hotplug_lock){++++}-{0:0}:        __lock_acquire+0x1298/0x1cd0        lock_acquire+0xc0/0x2b0        cpus_read_lock+0x2a/0xc0        static_key_slow_dec+0x16/0x60        __hugetlb_vmemmap_restore_folio+0x1b9/0x200        dissolve_free_huge_page+0x21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26987</guid>
    </item>
  </channel>
</rss>
