<?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 04:07:09 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64214</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64214</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-64214</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0954 — 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-0954</link>
      <description>certfr-2026-avi-0954</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0954</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64214</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64214</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() A kernel panic is observed when handling machine check exceptions from real mode.   BUG: Unable to handle kernel data access on read at 0xc00000006be21300   Oops: Kernel access of bad area, sig: 11 [#1]   MSR:  8000000000001003 &amp;lt;SF,ME,RI,LE&amp;gt;  CR: 88222248  XER: 00000005   CFAR: c00000000003ffc4 DAR: c00000006be21300 DSISR: 40000000 IRQMASK: 0   NIP [c000000000029e40] arch_irq_work_raise+0x10/0x70   LR [c00000000003ffc8] machine_check_queue_event+0xa8/0x150   Call Trace:   [c0000000179d3c70] [c00000000003ff64] machine_check_queue_event+0x44/0x150   [c0000000179d3d30] [c0000000000084e0] machine_check_early_common+0x1f0/0x2c0 The crash occurs because arch_irq_work_raise() calls preempt_disable() from machine check exception (MCE) handlers running in real mode. In this context, accessing the preempt_count can fault, leading to the panic. The preempt_disable()/preempt_enable() pair in arch_irq_work_raise() was originally added by commit 0fe1ac48bef0 (&amp;#34;powerpc/perf_event: Fix oops due to perf_event_do_pending call&amp;#34;) to avoid races while raising irq work from exception context. Later, commit 471ba0e686cb (&amp;#34;irq_work: Do not raise an IPI when queueing work on the local CPU&amp;#34;) added preemption protection in irq_work_queue() path, while commit 20b876918c06 (&amp;#34;irq_work: Use per cpu atomics instead of regular atomics&amp;#34;) added equivalent…&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise() A kernel panic is observed when handling machine check exceptions from real mode.   BUG: Unable to handle kernel data access on read at 0xc00000006be21300   Oops: Kernel access of bad area, sig: 11 [#1]   MSR:  8000000000001003 &amp;lt;SF,ME,RI,LE&amp;gt;  CR: 88222248  XER: 00000005   CFAR: c00000000003ffc4 DAR: c00000006be21300 DSISR: 40000000 IRQMASK: 0   NIP [c000000000029e40] arch_irq_work_raise+0x10/0x70   LR [c00000000003ffc8] machine_check_queue_event+0xa8/0x150   Call Trace:   [c0000000179d3c70] [c00000000003ff64] machine_check_queue_event+0x44/0x150   [c0000000179d3d30] [c0000000000084e0] machine_check_early_common+0x1f0/0x2c0 The crash occurs because arch_irq_work_raise() calls preempt_disable() from machine check exception (MCE) handlers running in real mode. In this context, accessing the preempt_count can fault, leading to the panic. The preempt_disable()/preempt_enable() pair in arch_irq_work_raise() was originally added by commit 0fe1ac48bef0 (&amp;#34;powerpc/perf_event: Fix oops due to perf_event_do_pending call&amp;#34;) to avoid races while raising irq work from exception context. Later, commit 471ba0e686cb (&amp;#34;irq_work: Do not raise an IPI when queueing work on the local CPU&amp;#34;) added preemption protection in irq_work_queue() path, while commit 20b876918c06 (&amp;#34;irq_work: Use per cpu atomics instead of regular atomics&amp;#34;) added equivalent…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64214</guid>
    </item>
  </channel>
</rss>
