<?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>Thu, 08 Oct 2026 23:18:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07405</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07405</link>
      <description>bdu:2025-07405</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07405</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-309687</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309687</link>
      <description>EUVD-2026-309687</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309687</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47349</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47349</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mwifiex: bring down link before deleting interface&lt;/p&gt;
&lt;p&gt;We can deadlock when rmmod&amp;#39;ing the driver or going through firmware
reset, because the cfg80211_unregister_wdev() has to bring down the link
for us, ... which then grab the same wiphy lock.&lt;/p&gt;
&lt;p&gt;nl80211_del_interface() already handles a very similar case, with a nice
description:&lt;/p&gt;
&lt;p&gt;/*
         * We hold RTNL, so this is safe, without RTNL opencount cannot
         * reach 0, and thus the rdev cannot be deleted.
         *
         * We need to do it for the dev_close(), since that will call
         * the netdev notifiers, and we need to acquire the mutex there
         * but don&amp;#39;t know if we get there from here or from some other
         * place (e.g. &amp;#34;ip link set ... down&amp;#34;).
         */
        mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx);
...&lt;/p&gt;
&lt;p&gt;Do similarly for mwifiex teardown, by ensuring we bring the link down
first.&lt;/p&gt;
&lt;p&gt;Sample deadlock trace:&lt;/p&gt;
&lt;p&gt;[  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds.
[  247.110630]       Not tainted 5.12.4 #5
[  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
[  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid:  2114 flags:0x00400208
[  247.133905] Call trace:
[  247.136644]  __switch_to+0x130/0x170
[  247.140643]  __schedule+0x714/0xa0c
[  247.144548]  schedule_preempt_disabled+0x88/0xf4
[  247.149714]  __mutex_lock_common+0x43c/0x750
[  247.154496]  mutex_lo…&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;mwifiex: bring down link before deleting interface&lt;/p&gt;
&lt;p&gt;We can deadlock when rmmod&amp;#39;ing the driver or going through firmware
reset, because the cfg80211_unregister_wdev() has to bring down the link
for us, ... which then grab the same wiphy lock.&lt;/p&gt;
&lt;p&gt;nl80211_del_interface() already handles a very similar case, with a nice
description:&lt;/p&gt;
&lt;p&gt;/*
         * We hold RTNL, so this is safe, without RTNL opencount cannot
         * reach 0, and thus the rdev cannot be deleted.
         *
         * We need to do it for the dev_close(), since that will call
         * the netdev notifiers, and we need to acquire the mutex there
         * but don&amp;#39;t know if we get there from here or from some other
         * place (e.g. &amp;#34;ip link set ... down&amp;#34;).
         */
        mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx);
...&lt;/p&gt;
&lt;p&gt;Do similarly for mwifiex teardown, by ensuring we bring the link down
first.&lt;/p&gt;
&lt;p&gt;Sample deadlock trace:&lt;/p&gt;
&lt;p&gt;[  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds.
[  247.110630]       Not tainted 5.12.4 #5
[  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
[  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid:  2114 flags:0x00400208
[  247.133905] Call trace:
[  247.136644]  __switch_to+0x130/0x170
[  247.140643]  __schedule+0x714/0xa0c
[  247.144548]  schedule_preempt_disabled+0x88/0xf4
[  247.149714]  __mutex_lock_common+0x43c/0x750
[  247.154496]  mutex_lo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47349</guid>
    </item>
    <item>
      <title>GHSA-x5fc-mwch-j73r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x5fc-mwch-j73r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mwifiex: bring down link before deleting interface&lt;/p&gt;
&lt;p&gt;We can deadlock when rmmod&amp;#39;ing the driver or going through firmware
reset, because the cfg80211_unregister_wdev() has to bring down the link
for us, ... which then grab the same wiphy lock.&lt;/p&gt;
&lt;p&gt;nl80211_del_interface() already handles a very similar case, with a nice
description:&lt;/p&gt;
&lt;p&gt;/*
         * We hold RTNL, so this is safe, without RTNL opencount cannot
         * reach 0, and thus the rdev cannot be deleted.
         *
         * We need to do it for the dev_close(), since that will call
         * the netdev notifiers, and we need to acquire the mutex there
         * but don&amp;#39;t know if we get there from here or from some other
         * place (e.g. &amp;#34;ip link set ... down&amp;#34;).
         */
        mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx);
...&lt;/p&gt;
&lt;p&gt;Do similarly for mwifiex teardown, by ensuring we bring the link down
first.&lt;/p&gt;
&lt;p&gt;Sample deadlock trace:&lt;/p&gt;
&lt;p&gt;[  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds.
[  247.110630]       Not tainted 5.12.4 #5
[  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
[  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid:  2114 flags:0x00400208
[  247.133905] Call trace:
[  247.136644]  __switch_to+0x130/0x170
[  247.140643]  __schedule+0x714/0xa0c
[  247.144548]  schedule_preempt_disabled+0x88/0xf4
[  247.149714]  __mutex_lock_common+0x43c/0x750
[  247.154496]  mutex_lo…&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;mwifiex: bring down link before deleting interface&lt;/p&gt;
&lt;p&gt;We can deadlock when rmmod&amp;#39;ing the driver or going through firmware
reset, because the cfg80211_unregister_wdev() has to bring down the link
for us, ... which then grab the same wiphy lock.&lt;/p&gt;
&lt;p&gt;nl80211_del_interface() already handles a very similar case, with a nice
description:&lt;/p&gt;
&lt;p&gt;/*
         * We hold RTNL, so this is safe, without RTNL opencount cannot
         * reach 0, and thus the rdev cannot be deleted.
         *
         * We need to do it for the dev_close(), since that will call
         * the netdev notifiers, and we need to acquire the mutex there
         * but don&amp;#39;t know if we get there from here or from some other
         * place (e.g. &amp;#34;ip link set ... down&amp;#34;).
         */
        mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx);
...&lt;/p&gt;
&lt;p&gt;Do similarly for mwifiex teardown, by ensuring we bring the link down
first.&lt;/p&gt;
&lt;p&gt;Sample deadlock trace:&lt;/p&gt;
&lt;p&gt;[  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds.
[  247.110630]       Not tainted 5.12.4 #5
[  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
[  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid:  2114 flags:0x00400208
[  247.133905] Call trace:
[  247.136644]  __switch_to+0x130/0x170
[  247.140643]  __schedule+0x714/0xa0c
[  247.144548]  schedule_preempt_disabled+0x88/0xf4
[  247.149714]  __mutex_lock_common+0x43c/0x750
[  247.154496]  mutex_lo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x5fc-mwch-j73r</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47349</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47349</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mwifiex: bring down link before deleting interface We can deadlock when rmmod&amp;#39;ing the driver or going through firmware reset, because the cfg80211_unregister_wdev() has to bring down the link for us, ... which then grab the same wiphy lock. nl80211_del_interface() already handles a very similar case, with a nice description:         /*          * We hold RTNL, so this is safe, without RTNL opencount cannot          * reach 0, and thus the rdev cannot be deleted.          *          * We need to do it for the dev_close(), since that will call          * the netdev notifiers, and we need to acquire the mutex there          * but don&amp;#39;t know if we get there from here or from some other          * place (e.g. &amp;#34;ip link set ... down&amp;#34;).          */         mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx); ... Do similarly for mwifiex teardown, by ensuring we bring the link down first. Sample deadlock trace: [  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds. [  247.110630]       Not tainted 5.12.4 #5 [  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message. [  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid: 2114 flags:0x00400208 [  247.133905] Call trace: [  247.136644]  __switch_to+0x130/0x170 [  247.140643]  __schedule+0x714/0xa0c [  247.144548]  schedule_preempt_disabled+0x88/0xf4 [  247.149714]  __mutex_lock_common+0x43c/0x750 [  247.154496]  mutex_lock_neste…&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mwifiex: bring down link before deleting interface We can deadlock when rmmod&amp;#39;ing the driver or going through firmware reset, because the cfg80211_unregister_wdev() has to bring down the link for us, ... which then grab the same wiphy lock. nl80211_del_interface() already handles a very similar case, with a nice description:         /*          * We hold RTNL, so this is safe, without RTNL opencount cannot          * reach 0, and thus the rdev cannot be deleted.          *          * We need to do it for the dev_close(), since that will call          * the netdev notifiers, and we need to acquire the mutex there          * but don&amp;#39;t know if we get there from here or from some other          * place (e.g. &amp;#34;ip link set ... down&amp;#34;).          */         mutex_unlock(&amp;amp;rdev-&amp;gt;wiphy.mtx); ... Do similarly for mwifiex teardown, by ensuring we bring the link down first. Sample deadlock trace: [  247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds. [  247.110630]       Not tainted 5.12.4 #5 [  247.115796] &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message. [  247.124557] task:rmmod           state:D stack:    0 pid: 2119 ppid: 2114 flags:0x00400208 [  247.133905] Call trace: [  247.136644]  __switch_to+0x130/0x170 [  247.140643]  __schedule+0x714/0xa0c [  247.144548]  schedule_preempt_disabled+0x88/0xf4 [  247.149714]  __mutex_lock_common+0x43c/0x750 [  247.154496]  mutex_lock_neste…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47349</guid>
    </item>
  </channel>
</rss>
