<?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 06:03:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64423</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64423</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-64423</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64423</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64423</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device&amp;#39;s multicast hash table (mc_hash). Since the device remains published in dev-&amp;gt;ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount is decremented. If the RCU callback runs and frees the group while a reader is accessing it, a use-after-free occurs. Fix this by unlinking the multicast group from mc_hash using ip_mc_hash_remove() before scheduling it for reclamation. BUG: KASAN: slab-use-after-free in ip_check_mc_rcu+0x149/0x3f0 Read of size 4 at addr ffff888009bf1408 by task mausezahn/2276 Call Trace:  &amp;lt;IRQ&amp;gt;  dump_stack_lvl+0x67/0x90  print_report+0x175/0x7c0  kasan_report+0x147/0x180  ip_check_mc_rcu+0x149/0x3f0  udp_v4_early_demux+0x36d/0x12d0  ip_rcv_finish_core+0xb8b/0x1390  ip_rcv_finish+0x54/0x120  NF_HOOK+0x213/0x2b0  __netif_receive_skb+0x126/0x340  process_backlog+0x4f2/0xf00  __napi_poll+0x92/0x2c0  net_rx_action+0x583/0xc60  handle_softirqs+0x236/0x7f0  do_softirq+0x57/0x80  &amp;lt;/IRQ&amp;gt; Allocated by task 2239:  kasan_save_track+0x3e/0x80  __kasan_kmalloc+0x72/0x90  ____ip_mc_inc_group+0x31a/0xa40  __ip_mc_join_g…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device&amp;#39;s multicast hash table (mc_hash). Since the device remains published in dev-&amp;gt;ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount is decremented. If the RCU callback runs and frees the group while a reader is accessing it, a use-after-free occurs. Fix this by unlinking the multicast group from mc_hash using ip_mc_hash_remove() before scheduling it for reclamation. BUG: KASAN: slab-use-after-free in ip_check_mc_rcu+0x149/0x3f0 Read of size 4 at addr ffff888009bf1408 by task mausezahn/2276 Call Trace:  &amp;lt;IRQ&amp;gt;  dump_stack_lvl+0x67/0x90  print_report+0x175/0x7c0  kasan_report+0x147/0x180  ip_check_mc_rcu+0x149/0x3f0  udp_v4_early_demux+0x36d/0x12d0  ip_rcv_finish_core+0xb8b/0x1390  ip_rcv_finish+0x54/0x120  NF_HOOK+0x213/0x2b0  __netif_receive_skb+0x126/0x340  process_backlog+0x4f2/0xf00  __napi_poll+0x92/0x2c0  net_rx_action+0x583/0xc60  handle_softirqs+0x236/0x7f0  do_softirq+0x57/0x80  &amp;lt;/IRQ&amp;gt; Allocated by task 2239:  kasan_save_track+0x3e/0x80  __kasan_kmalloc+0x72/0x90  ____ip_mc_inc_group+0x31a/0xa40  __ip_mc_join_g…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64423</guid>
    </item>
  </channel>
</rss>
