<?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>Sat, 03 Oct 2026 06:09:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12858</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12858</link>
      <description>bdu:2026-12858</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12858</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-43468</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43468</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-43468</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-315960</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315960</link>
      <description>EUVD-2026-315960</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315960</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43468</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43468</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5: Fix deadlock between devlink lock and esw-&amp;gt;wq&lt;/p&gt;
&lt;p&gt;esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt;
esw_vfs_changed_event_handler and acquires the devlink lock.&lt;/p&gt;
&lt;p&gt;.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt;
mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt;
mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks
when esw_vfs_changed_event_handler executes.&lt;/p&gt;
&lt;p&gt;Fix that by no longer flushing the work to avoid the deadlock, and using
a generation counter to keep track of work relevance. This avoids an old
handler manipulating an esw that has undergone one or more mode changes:
- the counter is incremented in mlx5_eswitch_event_handler_unregister.
- the counter is read and passed to the ephemeral mlx5_host_work struct.
- the work handler takes the devlink lock and bails out if the current
  generation is different than the one it was scheduled to operate on.
- mlx5_eswitch_cleanup does the final draining before destroying the wq.&lt;/p&gt;
&lt;p&gt;No longer flushing the workqueue has the side effect of maybe no longer
cancelling pending vport_change_handler work items, but that&amp;#39;s ok since
those are disabled elsewhere:
- mlx5_eswitch_disable_locked disables the vport eq notifier.
- mlx5_esw_vport_disable disarms the HW EQ notification and marks
  vport-&amp;gt;enabled under state_lock to false to prevent pending vport
  handler from doing anything.
- mlx5_eswitch_cleanup…&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: Fix deadlock between devlink lock and esw-&amp;gt;wq&lt;/p&gt;
&lt;p&gt;esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt;
esw_vfs_changed_event_handler and acquires the devlink lock.&lt;/p&gt;
&lt;p&gt;.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt;
mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt;
mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks
when esw_vfs_changed_event_handler executes.&lt;/p&gt;
&lt;p&gt;Fix that by no longer flushing the work to avoid the deadlock, and using
a generation counter to keep track of work relevance. This avoids an old
handler manipulating an esw that has undergone one or more mode changes:
- the counter is incremented in mlx5_eswitch_event_handler_unregister.
- the counter is read and passed to the ephemeral mlx5_host_work struct.
- the work handler takes the devlink lock and bails out if the current
  generation is different than the one it was scheduled to operate on.
- mlx5_eswitch_cleanup does the final draining before destroying the wq.&lt;/p&gt;
&lt;p&gt;No longer flushing the workqueue has the side effect of maybe no longer
cancelling pending vport_change_handler work items, but that&amp;#39;s ok since
those are disabled elsewhere:
- mlx5_eswitch_disable_locked disables the vport eq notifier.
- mlx5_esw_vport_disable disarms the HW EQ notification and marks
  vport-&amp;gt;enabled under state_lock to false to prevent pending vport
  handler from doing anything.
- mlx5_eswitch_cleanup…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43468</guid>
    </item>
    <item>
      <title>GHSA-7gc8-cffq-4r9r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7gc8-cffq-4r9r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5: Fix deadlock between devlink lock and esw-&amp;gt;wq&lt;/p&gt;
&lt;p&gt;esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt;
esw_vfs_changed_event_handler and acquires the devlink lock.&lt;/p&gt;
&lt;p&gt;.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt;
mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt;
mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks
when esw_vfs_changed_event_handler executes.&lt;/p&gt;
&lt;p&gt;Fix that by no longer flushing the work to avoid the deadlock, and using
a generation counter to keep track of work relevance. This avoids an old
handler manipulating an esw that has undergone one or more mode changes:
- the counter is incremented in mlx5_eswitch_event_handler_unregister.
- the counter is read and passed to the ephemeral mlx5_host_work struct.
- the work handler takes the devlink lock and bails out if the current
  generation is different than the one it was scheduled to operate on.
- mlx5_eswitch_cleanup does the final draining before destroying the wq.&lt;/p&gt;
&lt;p&gt;No longer flushing the workqueue has the side effect of maybe no longer
cancelling pending vport_change_handler work items, but that&amp;#39;s ok since
those are disabled elsewhere:
- mlx5_eswitch_disable_locked disables the vport eq notifier.
- mlx5_esw_vport_disable disarms the HW EQ notification and marks
  vport-&amp;gt;enabled under state_lock to false to prevent pending vport
  handler from doing anything.
- mlx5_eswitch_cleanup…&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: Fix deadlock between devlink lock and esw-&amp;gt;wq&lt;/p&gt;
&lt;p&gt;esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt;
esw_vfs_changed_event_handler and acquires the devlink lock.&lt;/p&gt;
&lt;p&gt;.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt;
mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt;
mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks
when esw_vfs_changed_event_handler executes.&lt;/p&gt;
&lt;p&gt;Fix that by no longer flushing the work to avoid the deadlock, and using
a generation counter to keep track of work relevance. This avoids an old
handler manipulating an esw that has undergone one or more mode changes:
- the counter is incremented in mlx5_eswitch_event_handler_unregister.
- the counter is read and passed to the ephemeral mlx5_host_work struct.
- the work handler takes the devlink lock and bails out if the current
  generation is different than the one it was scheduled to operate on.
- mlx5_eswitch_cleanup does the final draining before destroying the wq.&lt;/p&gt;
&lt;p&gt;No longer flushing the workqueue has the side effect of maybe no longer
cancelling pending vport_change_handler work items, but that&amp;#39;s ok since
those are disabled elsewhere:
- mlx5_eswitch_disable_locked disables the vport eq notifier.
- mlx5_esw_vport_disable disarms the HW EQ notification and marks
  vport-&amp;gt;enabled under state_lock to false to prevent pending vport
  handler from doing anything.
- mlx5_eswitch_cleanup…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7gc8-cffq-4r9r</guid>
    </item>
    <item>
      <title>OESA-2026-2582 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2582</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mISDN: hfcpci: Fix warning when deleting uninitialized timer&lt;/p&gt;
&lt;p&gt;With CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads
to the following splat:&lt;/p&gt;
&lt;p&gt;[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0
[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0
[  250.218775] Modules linked in: hfcpci(-) mISDN_core
[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)
[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0
[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d
[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286
[  250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95
[  250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0
[  250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39
[  250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001
[  250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8
[  250.232454] FS:  00007f3208f01540(0000) GS:ff…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mISDN: hfcpci: Fix warning when deleting uninitialized timer&lt;/p&gt;
&lt;p&gt;With CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads
to the following splat:&lt;/p&gt;
&lt;p&gt;[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0
[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0
[  250.218775] Modules linked in: hfcpci(-) mISDN_core
[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)
[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0
[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d
[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286
[  250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95
[  250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0
[  250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39
[  250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001
[  250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8
[  250.232454] FS:  00007f3208f01540(0000) GS:ff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2582</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21388-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22742-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22742-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43468</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43468</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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix deadlock between devlink lock and esw-&amp;gt;wq esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt; esw_vfs_changed_event_handler and acquires the devlink lock. .eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt; mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt; mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks when esw_vfs_changed_event_handler executes. Fix that by no longer flushing the work to avoid the deadlock, and using a generation counter to keep track of work relevance. This avoids an old handler manipulating an esw that has undergone one or more mode changes: - the counter is incremented in mlx5_eswitch_event_handler_unregister. - the counter is read and passed to the ephemeral mlx5_host_work struct. - the work handler takes the devlink lock and bails out if the current   generation is different than the one it was scheduled to operate on. - mlx5_eswitch_cleanup does the final draining before destroying the wq. No longer flushing the workqueue has the side effect of maybe no longer cancelling pending vport_change_handler work items, but that&amp;#39;s ok since those are disabled elsewhere: - mlx5_eswitch_disable_locked disables the vport eq notifier. - mlx5_esw_vport_disable disarms the HW EQ notification and marks   vport-&amp;gt;enabled under state_lock to false to prevent pending vport   handler from doing anything. - mlx5_eswitch_cleanup dest…&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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix deadlock between devlink lock and esw-&amp;gt;wq esw-&amp;gt;work_queue executes esw_functions_changed_event_handler -&amp;gt; esw_vfs_changed_event_handler and acquires the devlink lock. .eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -&amp;gt; mlx5_devlink_eswitch_mode_set -&amp;gt; mlx5_eswitch_disable_locked -&amp;gt; mlx5_eswitch_event_handler_unregister -&amp;gt; flush_workqueue deadlocks when esw_vfs_changed_event_handler executes. Fix that by no longer flushing the work to avoid the deadlock, and using a generation counter to keep track of work relevance. This avoids an old handler manipulating an esw that has undergone one or more mode changes: - the counter is incremented in mlx5_eswitch_event_handler_unregister. - the counter is read and passed to the ephemeral mlx5_host_work struct. - the work handler takes the devlink lock and bails out if the current   generation is different than the one it was scheduled to operate on. - mlx5_eswitch_cleanup does the final draining before destroying the wq. No longer flushing the workqueue has the side effect of maybe no longer cancelling pending vport_change_handler work items, but that&amp;#39;s ok since those are disabled elsewhere: - mlx5_eswitch_disable_locked disables the vport eq notifier. - mlx5_esw_vport_disable disarms the HW EQ notification and marks   vport-&amp;gt;enabled under state_lock to false to prevent pending vport   handler from doing anything. - mlx5_eswitch_cleanup dest…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43468</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1454 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1454</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 Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&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 Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1454</guid>
    </item>
  </channel>
</rss>
