<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:11:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98881</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98881</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://cve.radiocsirt.org/vuln/bell-cve-2026-98881</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://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>EUVD-2026-392148</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392148</link>
      <description>EUVD-2026-392148</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392148</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98881</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98881</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: remove stale rcu_barrier() in br_multicast_dev_del()&lt;/p&gt;
&lt;p&gt;This rcu_barrier() came from a time call_rcu() calls were used in
net/bridge/br_multicast.c.&lt;/p&gt;
&lt;p&gt;Now kfree_rcu() is there, we can remove this problematic rcu_barrier()
which causes extreme RTNL pressure in many syzbot reports.&lt;/p&gt;
&lt;p&gt;INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537.
task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2      task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337
Workqueue: netns cleanup_net
Call Trace:
 &amp;lt;TASK&amp;gt;
  [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483
  [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411
  [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]
  [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529
  [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75
  [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153
  [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888
  [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459
  [&amp;lt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: remove stale rcu_barrier() in br_multicast_dev_del()&lt;/p&gt;
&lt;p&gt;This rcu_barrier() came from a time call_rcu() calls were used in
net/bridge/br_multicast.c.&lt;/p&gt;
&lt;p&gt;Now kfree_rcu() is there, we can remove this problematic rcu_barrier()
which causes extreme RTNL pressure in many syzbot reports.&lt;/p&gt;
&lt;p&gt;INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537.
task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2      task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337
Workqueue: netns cleanup_net
Call Trace:
 &amp;lt;TASK&amp;gt;
  [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483
  [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411
  [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]
  [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529
  [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75
  [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153
  [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888
  [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459
  [&amp;lt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98881</guid>
    </item>
    <item>
      <title>GHSA-52xp-vqwj-rp88</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-52xp-vqwj-rp88</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: remove stale rcu_barrier() in br_multicast_dev_del()&lt;/p&gt;
&lt;p&gt;This rcu_barrier() came from a time call_rcu() calls were used in
net/bridge/br_multicast.c.&lt;/p&gt;
&lt;p&gt;Now kfree_rcu() is there, we can remove this problematic rcu_barrier()
which causes extreme RTNL pressure in many syzbot reports.&lt;/p&gt;
&lt;p&gt;INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537.
task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2      task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337
Workqueue: netns cleanup_net
Call Trace:
 &amp;lt;TASK&amp;gt;
  [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483
  [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411
  [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]
  [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529
  [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75
  [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153
  [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888
  [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459
  [&amp;lt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bridge: remove stale rcu_barrier() in br_multicast_dev_del()&lt;/p&gt;
&lt;p&gt;This rcu_barrier() came from a time call_rcu() calls were used in
net/bridge/br_multicast.c.&lt;/p&gt;
&lt;p&gt;Now kfree_rcu() is there, we can remove this problematic rcu_barrier()
which causes extreme RTNL pressure in many syzbot reports.&lt;/p&gt;
&lt;p&gt;INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537.
task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2      task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337
Workqueue: netns cleanup_net
Call Trace:
 &amp;lt;TASK&amp;gt;
  [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483
  [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411
  [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]
  [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529
  [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75
  [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]
  [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153
  [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888
  [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459
  [&amp;lt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-52xp-vqwj-rp88</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98881 — net: bridge: remove stale rcu_barrier() in br_multicast_dev_del()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98881</link>
      <description>msrc_CVE-2026-98881</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98881</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98881</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98881</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 221 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: remove stale rcu_barrier() in br_multicast_dev_del() This rcu_barrier() came from a time call_rcu() calls were used in net/bridge/br_multicast.c. Now kfree_rcu() is there, we can remove this problematic rcu_barrier() which causes extreme RTNL pressure in many syzbot reports. INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537. task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2 task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337 Workqueue: netns cleanup_net Call Trace:  &amp;lt;TASK&amp;gt;   [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483   [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411   [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]   [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529   [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75   [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153   [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888   [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459   [&amp;lt;ffffffff8…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 221 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: remove stale rcu_barrier() in br_multicast_dev_del() This rcu_barrier() came from a time call_rcu() calls were used in net/bridge/br_multicast.c. Now kfree_rcu() is there, we can remove this problematic rcu_barrier() which causes extreme RTNL pressure in many syzbot reports. INFO: task syz-executor:77945 is blocked on a mutex likely owned by task kworker/u1024:5:36537. task:kworker/u1024:5 state:D stack:24616 pid:36537 tgid:36537 ppid:2 task_flags:0x4208060 flags:0x00080000 last_sleep:612797637337 Workqueue: netns cleanup_net Call Trace:  &amp;lt;TASK&amp;gt;   [&amp;lt;ffffffff81914eaa&amp;gt;] context_switch+0xf2a/0x1730 kernel/sched/core.c:6483   [&amp;lt;ffffffff81201143&amp;gt;] __schedule+0x1133/0x43a0 kernel/sched/core.c:8411   [&amp;lt;ffffffff8120446b&amp;gt;] __schedule_loop kernel/sched/core.c:8514 [inline]   [&amp;lt;ffffffff8120446b&amp;gt;] schedule+0xab/0x260 kernel/sched/core.c:8529   [&amp;lt;ffffffff8121a093&amp;gt;] schedule_timeout+0xc3/0x2b0 kernel/time/sleep_timeout.c:75   [&amp;lt;ffffffff81205347&amp;gt;] do_wait_for_common kernel/sched/completion.c:100 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] __wait_for_common kernel/sched/completion.c:121 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] wait_for_common kernel/sched/completion.c:132 [inline]   [&amp;lt;ffffffff81205347&amp;gt;] wait_for_completion+0x2c7/0x5d0 kernel/sched/completion.c:153   [&amp;lt;ffffffff81b8f27f&amp;gt;] rcu_barrier+0x49f/0x620 kernel/rcu/tree.c:3888   [&amp;lt;ffffffff860091b3&amp;gt;] br_multicast_dev_del+0x303/0x350 net/bridge/br_multicast.c:4459   [&amp;lt;ffffffff8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98881</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
