<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 15:46:54 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98014</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98014</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5: E-Switch, prevent mc_list repopulation during vport disable&lt;/p&gt;
&lt;p&gt;In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead
of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is
NULL before the change handler observes it.&lt;/p&gt;
&lt;p&gt;During FW-fatal recovery the disable runs while dev-&amp;gt;state ==
INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()
fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so
esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries
to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB
by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the
FDB with those refs still held, corrupting the sub-tree and
leaving dangling flow_rule pointers in vport-&amp;gt;mc_list.&lt;/p&gt;
&lt;p&gt;Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:&lt;/p&gt;
&lt;p&gt;refcount_t: underflow; use-after-free.
   tree_put_node+0xef/0x110 [mlx5_core]
   clean_tree+0x44/0xd0 [mlx5_core] (x5)
   mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]
   mlx5_unload+0x65/0xd0 [mlx5_core]
   ... mlx5_health_try_recover&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000003000055
   down_write+0x1c/0x60
   mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]
   esw_del_mc_addr+0x7b/0x170 [mlx5_core]
   esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]
   esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]
   mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]
   ... mlx5_load ... mlx5_health_try_…&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/mlx5: E-Switch, prevent mc_list repopulation during vport disable&lt;/p&gt;
&lt;p&gt;In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead
of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is
NULL before the change handler observes it.&lt;/p&gt;
&lt;p&gt;During FW-fatal recovery the disable runs while dev-&amp;gt;state ==
INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()
fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so
esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries
to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB
by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the
FDB with those refs still held, corrupting the sub-tree and
leaving dangling flow_rule pointers in vport-&amp;gt;mc_list.&lt;/p&gt;
&lt;p&gt;Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:&lt;/p&gt;
&lt;p&gt;refcount_t: underflow; use-after-free.
   tree_put_node+0xef/0x110 [mlx5_core]
   clean_tree+0x44/0xd0 [mlx5_core] (x5)
   mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]
   mlx5_unload+0x65/0xd0 [mlx5_core]
   ... mlx5_health_try_recover&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000003000055
   down_write+0x1c/0x60
   mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]
   esw_del_mc_addr+0x7b/0x170 [mlx5_core]
   esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]
   esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]
   mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]
   ... mlx5_load ... mlx5_health_try_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98014</guid>
    </item>
    <item>
      <title>GHSA-hjxx-jpr5-hfgw</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hjxx-jpr5-hfgw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5: E-Switch, prevent mc_list repopulation during vport disable&lt;/p&gt;
&lt;p&gt;In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead
of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is
NULL before the change handler observes it.&lt;/p&gt;
&lt;p&gt;During FW-fatal recovery the disable runs while dev-&amp;gt;state ==
INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()
fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so
esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries
to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB
by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the
FDB with those refs still held, corrupting the sub-tree and
leaving dangling flow_rule pointers in vport-&amp;gt;mc_list.&lt;/p&gt;
&lt;p&gt;Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:&lt;/p&gt;
&lt;p&gt;refcount_t: underflow; use-after-free.
   tree_put_node+0xef/0x110 [mlx5_core]
   clean_tree+0x44/0xd0 [mlx5_core] (x5)
   mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]
   mlx5_unload+0x65/0xd0 [mlx5_core]
   ... mlx5_health_try_recover&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000003000055
   down_write+0x1c/0x60
   mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]
   esw_del_mc_addr+0x7b/0x170 [mlx5_core]
   esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]
   esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]
   mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]
   ... mlx5_load ... mlx5_health_try_…&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/mlx5: E-Switch, prevent mc_list repopulation during vport disable&lt;/p&gt;
&lt;p&gt;In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead
of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is
NULL before the change handler observes it.&lt;/p&gt;
&lt;p&gt;During FW-fatal recovery the disable runs while dev-&amp;gt;state ==
INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()
fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so
esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries
to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB
by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the
FDB with those refs still held, corrupting the sub-tree and
leaving dangling flow_rule pointers in vport-&amp;gt;mc_list.&lt;/p&gt;
&lt;p&gt;Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:&lt;/p&gt;
&lt;p&gt;refcount_t: underflow; use-after-free.
   tree_put_node+0xef/0x110 [mlx5_core]
   clean_tree+0x44/0xd0 [mlx5_core] (x5)
   mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]
   mlx5_unload+0x65/0xd0 [mlx5_core]
   ... mlx5_health_try_recover&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000003000055
   down_write+0x1c/0x60
   mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]
   esw_del_mc_addr+0x7b/0x170 [mlx5_core]
   esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]
   esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]
   mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]
   ... mlx5_load ... mlx5_health_try_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hjxx-jpr5-hfgw</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98014</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98014</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-Switch, prevent mc_list repopulation during vport disable In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is NULL before the change handler observes it. During FW-fatal recovery the disable runs while dev-&amp;gt;state == INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode() fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the FDB with those refs still held, corrupting the sub-tree and leaving dangling flow_rule pointers in vport-&amp;gt;mc_list. Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:   refcount_t: underflow; use-after-free.    tree_put_node+0xef/0x110 [mlx5_core]    clean_tree+0x44/0xd0 [mlx5_core] (x5)    mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]    mlx5_unload+0x65/0xd0 [mlx5_core]    ... mlx5_health_try_recover   BUG: unable to handle page fault for address: 0000000003000055    down_write+0x1c/0x60    mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]    esw_del_mc_addr+0x7b/0x170 [mlx5_core]    esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]    esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]    mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]    ... mlx5_load ... mlx5_health_try_recove…&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-Switch, prevent mc_list repopulation during vport disable In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead of esw_vport_change_handle_locked() so vport-&amp;gt;allmulti_rule is NULL before the change handler observes it. During FW-fatal recovery the disable runs while dev-&amp;gt;state == INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode() fails and returns early, leaving vport-&amp;gt;allmulti_rule intact, so esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries to vport-&amp;gt;mc_list whose flow rules are then installed in the FDB by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the FDB with those refs still held, corrupting the sub-tree and leaving dangling flow_rule pointers in vport-&amp;gt;mc_list. Two-stage failure on `echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;bdf&amp;gt;/reset`:   refcount_t: underflow; use-after-free.    tree_put_node+0xef/0x110 [mlx5_core]    clean_tree+0x44/0xd0 [mlx5_core] (x5)    mlx5_fs_core_cleanup+0x57/0x1c0 [mlx5_core]    mlx5_unload+0x65/0xd0 [mlx5_core]    ... mlx5_health_try_recover   BUG: unable to handle page fault for address: 0000000003000055    down_write+0x1c/0x60    mlx5_del_flow_rules+0x33/0x1f0 [mlx5_core]    esw_del_mc_addr+0x7b/0x170 [mlx5_core]    esw_apply_vport_addr_list+0x56/0xf0 [mlx5_core]    esw_vport_change_handle_locked+0x28b/0x310 [mlx5_core]    mlx5_esw_vport_enable+0x270/0x4a0 [mlx5_core]    ... mlx5_load ... mlx5_health_try_recove…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98014</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
