<?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 16:50:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80776</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80776</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-80776</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-80776</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80776</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: futex: Fix race in futex_pivot_pending() during private hash resize A task performing a custom private hash resize can remain blocked in uninterruptible sleep indefinitely.  The hung-task detector reports:   INFO: task futex-resizer:314 blocked for more than 10 seconds.   task:futex-resizer state:D stack:14824 pid:314 tgid:312 ppid:311   Call Trace:    __schedule+0x521/0xf30    schedule+0x22/0xa0    futex_hash_allocate+0x3db/0x490    __do_sys_prctl+0x6f5/0xbd0    do_syscall_64+0xf9/0x530    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: hung_task: blocked tasks futex_pivot_pending() allows the resize request to continue when either no replacement hash is pending (hash_new == NULL) or the current hash reference count has reached zero. After the final-reference wake, another futex task can complete the pivot between the two observations:   T1                                  T2   futex_hash_allocate()     wait_var_event(mm, ...)       futex_pivot_pending(mm)         hash_new != NULL                                       futex_hash()                                         futex_ref_get(old) -&amp;gt; false                                         futex_pivot_hash(mm)                                           hash_new = NULL                                           __futex_pivot_hash(mm, new)                                             rcu_assign_pointer(hash, new)         fph = rcu_dereference…&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: futex: Fix race in futex_pivot_pending() during private hash resize A task performing a custom private hash resize can remain blocked in uninterruptible sleep indefinitely.  The hung-task detector reports:   INFO: task futex-resizer:314 blocked for more than 10 seconds.   task:futex-resizer state:D stack:14824 pid:314 tgid:312 ppid:311   Call Trace:    __schedule+0x521/0xf30    schedule+0x22/0xa0    futex_hash_allocate+0x3db/0x490    __do_sys_prctl+0x6f5/0xbd0    do_syscall_64+0xf9/0x530    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: hung_task: blocked tasks futex_pivot_pending() allows the resize request to continue when either no replacement hash is pending (hash_new == NULL) or the current hash reference count has reached zero. After the final-reference wake, another futex task can complete the pivot between the two observations:   T1                                  T2   futex_hash_allocate()     wait_var_event(mm, ...)       futex_pivot_pending(mm)         hash_new != NULL                                       futex_hash()                                         futex_ref_get(old) -&amp;gt; false                                         futex_pivot_hash(mm)                                           hash_new = NULL                                           __futex_pivot_hash(mm, new)                                             rcu_assign_pointer(hash, new)         fph = rcu_dereference…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80776</guid>
    </item>
  </channel>
</rss>
