<?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:13:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37929</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37929</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: 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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-37929</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0464 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</link>
      <description>certfr-2025-avi-0464</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37929</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37929</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 76 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays Commit a5951389e58d (&amp;#34;arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists&amp;#34;) added some additional CPUs to the Spectre-BHB workaround, including some new arrays for designs that require new &amp;#39;k&amp;#39; values for the workaround to be effective. Unfortunately, the new arrays omitted the sentinel entry and so is_midr_in_range_list() will walk off the end when it doesn&amp;#39;t find a match. With UBSAN enabled, this leads to a crash during boot when is_midr_in_range_list() is inlined (which was more common prior to c8c2647e69be (&amp;#34;arm64: Make  _midr_in_range_list() an exported function&amp;#34;)):  |  Internal error: aarch64 BRK: 00000000f2000001 [#1] PREEMPT SMP  |  pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  |  pc : spectre_bhb_loop_affected+0x28/0x30  |  lr : is_spectre_bhb_affected+0x170/0x190  | [...]  |  Call trace:  |   spectre_bhb_loop_affected+0x28/0x30  |   update_cpu_capabilities+0xc0/0x184  |   init_cpu_features+0x188/0x1a4  |   cpuinfo_store_boot_cpu+0x4c/0x60  |   smp_prepare_boot_cpu+0x38/0x54  |   start_kernel+0x8c/0x478  |   __primary_switched+0xc8/0xd4  |  Code: 6b09011f 54000061 52801080 d65f03c0 (d4200020)  |  ---[ end trace 0000000000000000 ]---  |  Kernel panic - not syncing: aarch64 BRK: Fatal exception Add the missing sentinel entries.&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 76 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays Commit a5951389e58d (&amp;#34;arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists&amp;#34;) added some additional CPUs to the Spectre-BHB workaround, including some new arrays for designs that require new &amp;#39;k&amp;#39; values for the workaround to be effective. Unfortunately, the new arrays omitted the sentinel entry and so is_midr_in_range_list() will walk off the end when it doesn&amp;#39;t find a match. With UBSAN enabled, this leads to a crash during boot when is_midr_in_range_list() is inlined (which was more common prior to c8c2647e69be (&amp;#34;arm64: Make  _midr_in_range_list() an exported function&amp;#34;)):  |  Internal error: aarch64 BRK: 00000000f2000001 [#1] PREEMPT SMP  |  pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  |  pc : spectre_bhb_loop_affected+0x28/0x30  |  lr : is_spectre_bhb_affected+0x170/0x190  | [...]  |  Call trace:  |   spectre_bhb_loop_affected+0x28/0x30  |   update_cpu_capabilities+0xc0/0x184  |   init_cpu_features+0x188/0x1a4  |   cpuinfo_store_boot_cpu+0x4c/0x60  |   smp_prepare_boot_cpu+0x38/0x54  |   start_kernel+0x8c/0x478  |   __primary_switched+0xc8/0xd4  |  Code: 6b09011f 54000061 52801080 d65f03c0 (d4200020)  |  ---[ end trace 0000000000000000 ]---  |  Kernel panic - not syncing: aarch64 BRK: Fatal exception Add the missing sentinel entries.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37929</guid>
    </item>
  </channel>
</rss>
