<?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 08:41:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74477</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74477</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-74477</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — 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-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74477</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74477</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: uprobes: Fix NULL pointer dereference in hprobe_expire() Forking a task that has a pending uretprobe can oops the kernel with a NULL pointer dereference in the clone() path:   BUG: kernel NULL pointer dereference, address: 0000000000000018   Oops: 0002 [#1] SMP NOPTI   RIP: 0010:hprobe_expire   CR2: 0000000000000018   Call Trace:    uprobe_copy_process    copy_process    kernel_clone    __x64_sys_clone    do_syscall_64    entry_SYSCALL_64_after_hwframe This was found on real hosts on Meta fleet. I&amp;#39;ve got the impression that this is what is happening:   CPU 1                          CPU 2 (traced task)   -----                          -------------------                                  hit uprobe, prepare_uretprobe():                                    hprobe LEASED, refcount &amp;gt;= 1   uprobe_unregister()     put_uprobe(): refcount -&amp;gt; 0                                  fork() -&amp;gt; dup_utask()                                    hprobe_expire(hprobe, true)                                      try_get_uprobe() -&amp;gt; NULL                                      get_uprobe(NULL)   &amp;lt;-- Oops Only take the extra reference when the uprobe is non-NULL; a NULL means it is gone and is the correct value to return.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: uprobes: Fix NULL pointer dereference in hprobe_expire() Forking a task that has a pending uretprobe can oops the kernel with a NULL pointer dereference in the clone() path:   BUG: kernel NULL pointer dereference, address: 0000000000000018   Oops: 0002 [#1] SMP NOPTI   RIP: 0010:hprobe_expire   CR2: 0000000000000018   Call Trace:    uprobe_copy_process    copy_process    kernel_clone    __x64_sys_clone    do_syscall_64    entry_SYSCALL_64_after_hwframe This was found on real hosts on Meta fleet. I&amp;#39;ve got the impression that this is what is happening:   CPU 1                          CPU 2 (traced task)   -----                          -------------------                                  hit uprobe, prepare_uretprobe():                                    hprobe LEASED, refcount &amp;gt;= 1   uprobe_unregister()     put_uprobe(): refcount -&amp;gt; 0                                  fork() -&amp;gt; dup_utask()                                    hprobe_expire(hprobe, true)                                      try_get_uprobe() -&amp;gt; NULL                                      get_uprobe(NULL)   &amp;lt;-- Oops Only take the extra reference when the uprobe is non-NULL; a NULL means it is gone and is the correct value to return.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74477</guid>
    </item>
  </channel>
</rss>
