<?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>Fri, 20 Nov 2026 23:34:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-22989</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-22989</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-22989</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — 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-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-22989</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-22989</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: check that server is running in unlock_filesystem If we are trying to unlock the filesystem via an administrative interface and nfsd isn&amp;#39;t running, it crashes the server. This happens currently because nfsd4_revoke_states() access state structures (eg., conf_id_hashtbl) that has been freed as a part of the server shutdown. [   59.465072] Call trace: [   59.465308]  nfsd4_revoke_states+0x1b4/0x898 [nfsd] (P) [   59.465830]  write_unlock_fs+0x258/0x440 [nfsd] [   59.466278]  nfsctl_transaction_write+0xb0/0x120 [nfsd] [   59.466780]  vfs_write+0x1f0/0x938 [   59.467088]  ksys_write+0xfc/0x1f8 [   59.467395]  __arm64_sys_write+0x74/0xb8 [   59.467746]  invoke_syscall.constprop.0+0xdc/0x1e8 [   59.468177]  do_el0_svc+0x154/0x1d8 [   59.468489]  el0_svc+0x40/0xe0 [   59.468767]  el0t_64_sync_handler+0xa0/0xe8 [   59.469138]  el0t_64_sync+0x1ac/0x1b0 Ensure this can&amp;#39;t happen by taking the nfsd_mutex and checking that the server is still up, and then holding the mutex across the call to nfsd4_revoke_states().&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: check that server is running in unlock_filesystem If we are trying to unlock the filesystem via an administrative interface and nfsd isn&amp;#39;t running, it crashes the server. This happens currently because nfsd4_revoke_states() access state structures (eg., conf_id_hashtbl) that has been freed as a part of the server shutdown. [   59.465072] Call trace: [   59.465308]  nfsd4_revoke_states+0x1b4/0x898 [nfsd] (P) [   59.465830]  write_unlock_fs+0x258/0x440 [nfsd] [   59.466278]  nfsctl_transaction_write+0xb0/0x120 [nfsd] [   59.466780]  vfs_write+0x1f0/0x938 [   59.467088]  ksys_write+0xfc/0x1f8 [   59.467395]  __arm64_sys_write+0x74/0xb8 [   59.467746]  invoke_syscall.constprop.0+0xdc/0x1e8 [   59.468177]  do_el0_svc+0x154/0x1d8 [   59.468489]  el0_svc+0x40/0xe0 [   59.468767]  el0t_64_sync_handler+0xa0/0xe8 [   59.469138]  el0t_64_sync+0x1ac/0x1b0 Ensure this can&amp;#39;t happen by taking the nfsd_mutex and checking that the server is still up, and then holding the mutex across the call to nfsd4_revoke_states().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-22989</guid>
    </item>
  </channel>
</rss>
