<?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 16:09:04 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98073</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98073</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;syzbot reported the warning in cfg80211_pernet_exit(). [0]&lt;/p&gt;
&lt;p&gt;The repro does the following:&lt;/p&gt;
&lt;p&gt;1. create two device in root netns and non-root netns
  2. assign the same altname for the two devices
  3. remove the non-root netns&lt;/p&gt;
&lt;p&gt;Since commit 7663d522099e (&amp;#34;net: check for altname conflicts
when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and
cfg802154_switch_netns() fail if init_net has a device with the
conflicting altname.&lt;/p&gt;
&lt;p&gt;default_device_exit_net() had the same issue and commit d09486a04f5d
(&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it.&lt;/p&gt;
&lt;p&gt;cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s generalise the fix by removing conflicting altnames for dying
netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;[0]:
cfg80211_switch_netns(rdev, &amp;amp;init_net)
WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160
Modules linked in:
CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: netns cleanup_net
RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871
Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90…&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: Remove conflicting altnames for dying netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;syzbot reported the warning in cfg80211_pernet_exit(). [0]&lt;/p&gt;
&lt;p&gt;The repro does the following:&lt;/p&gt;
&lt;p&gt;1. create two device in root netns and non-root netns
  2. assign the same altname for the two devices
  3. remove the non-root netns&lt;/p&gt;
&lt;p&gt;Since commit 7663d522099e (&amp;#34;net: check for altname conflicts
when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and
cfg802154_switch_netns() fail if init_net has a device with the
conflicting altname.&lt;/p&gt;
&lt;p&gt;default_device_exit_net() had the same issue and commit d09486a04f5d
(&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it.&lt;/p&gt;
&lt;p&gt;cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s generalise the fix by removing conflicting altnames for dying
netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;[0]:
cfg80211_switch_netns(rdev, &amp;amp;init_net)
WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160
Modules linked in:
CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: netns cleanup_net
RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871
Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98073</guid>
    </item>
    <item>
      <title>GHSA-g33p-j5vg-7cwx</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-g33p-j5vg-7cwx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;syzbot reported the warning in cfg80211_pernet_exit(). [0]&lt;/p&gt;
&lt;p&gt;The repro does the following:&lt;/p&gt;
&lt;p&gt;1. create two device in root netns and non-root netns
  2. assign the same altname for the two devices
  3. remove the non-root netns&lt;/p&gt;
&lt;p&gt;Since commit 7663d522099e (&amp;#34;net: check for altname conflicts
when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and
cfg802154_switch_netns() fail if init_net has a device with the
conflicting altname.&lt;/p&gt;
&lt;p&gt;default_device_exit_net() had the same issue and commit d09486a04f5d
(&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it.&lt;/p&gt;
&lt;p&gt;cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s generalise the fix by removing conflicting altnames for dying
netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;[0]:
cfg80211_switch_netns(rdev, &amp;amp;init_net)
WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160
Modules linked in:
CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: netns cleanup_net
RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871
Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90…&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: Remove conflicting altnames for dying netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;syzbot reported the warning in cfg80211_pernet_exit(). [0]&lt;/p&gt;
&lt;p&gt;The repro does the following:&lt;/p&gt;
&lt;p&gt;1. create two device in root netns and non-root netns
  2. assign the same altname for the two devices
  3. remove the non-root netns&lt;/p&gt;
&lt;p&gt;Since commit 7663d522099e (&amp;#34;net: check for altname conflicts
when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and
cfg802154_switch_netns() fail if init_net has a device with the
conflicting altname.&lt;/p&gt;
&lt;p&gt;default_device_exit_net() had the same issue and commit d09486a04f5d
(&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it.&lt;/p&gt;
&lt;p&gt;cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s generalise the fix by removing conflicting altnames for dying
netns in __dev_change_net_namespace().&lt;/p&gt;
&lt;p&gt;[0]:
cfg80211_switch_netns(rdev, &amp;amp;init_net)
WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160
Modules linked in:
CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: netns cleanup_net
RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871
Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-g33p-j5vg-7cwx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98073</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98073</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: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). syzbot reported the warning in cfg80211_pernet_exit(). [0] The repro does the following:   1. create two device in root netns and non-root netns   2. assign the same altname for the two devices   3. remove the non-root netns Since commit 7663d522099e (&amp;#34;net: check for altname conflicts when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and cfg802154_switch_netns() fail if init_net has a device with the conflicting altname. default_device_exit_net() had the same issue and commit d09486a04f5d (&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it. cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix. Let&amp;#39;s generalise the fix by removing conflicting altnames for dying netns in __dev_change_net_namespace(). [0]: cfg80211_switch_netns(rdev, &amp;amp;init_net) WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160 Modules linked in: CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: netns cleanup_net RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871 Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90 eb cc e8…&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: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). syzbot reported the warning in cfg80211_pernet_exit(). [0] The repro does the following:   1. create two device in root netns and non-root netns   2. assign the same altname for the two devices   3. remove the non-root netns Since commit 7663d522099e (&amp;#34;net: check for altname conflicts when changing netdev&amp;#39;s netns&amp;#34;), cfg80211_switch_netns() and cfg802154_switch_netns() fail if init_net has a device with the conflicting altname. default_device_exit_net() had the same issue and commit d09486a04f5d (&amp;#34;net: fix removing a namespace with conflicting altnames&amp;#34;) fixed it. cfg80211_pernet_exit() and cfg802154_pernet_exit() need the same fix. Let&amp;#39;s generalise the fix by removing conflicting altnames for dying netns in __dev_change_net_namespace(). [0]: cfg80211_switch_netns(rdev, &amp;amp;init_net) WARNING: net/wireless/core.c:1871 at cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871, CPU#1: kworker/u8:9/1160 Modules linked in: CPU: 1 UID: 0 PID: 1160 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: netns cleanup_net RIP: 0010:cfg80211_pernet_exit+0xd5/0x120 net/wireless/core.c:1871 Code: e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 b4 ef 0e f7 4d 8b 36 49 81 fe 20 10 4a 90 74 12 e8 03 3d 9f f6 eb 85 e8 fc 3c 9f f6 90 &amp;lt;0f&amp;gt; 0b 90 eb cc e8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98073</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>
