<?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 10:12:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-54159</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54159</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-54159</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-312398</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312398</link>
      <description>EUVD-2026-312398</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312398</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54159</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54159</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: mtu3: fix kernel panic at qmu transfer done irq handler&lt;/p&gt;
&lt;p&gt;When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back
request, if another thread handle disconnect event at the same time, and
try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu
irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before
handling it.&lt;/p&gt;
&lt;p&gt;e.g.
qmu done irq on cpu0                 thread running on cpu1&lt;/p&gt;
&lt;p&gt;qmu_done_tx()
  handle gpd [0]
    mtu3_requ_complete()        mtu3_gadget_ep_disable()
      unlock @mtu-&amp;gt;lock
        give back request         lock @mtu-&amp;gt;lock
                                    mtu3_ep_disable()
                                      mtu3_gpd_ring_free()
                                   unlock @mtu-&amp;gt;lock
      lock @mtu-&amp;gt;lock
    get next gpd [1]&lt;/p&gt;
&lt;p&gt;[1]: goto [0] to handle next gpd, and next gpd may be NULL.&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;usb: mtu3: fix kernel panic at qmu transfer done irq handler&lt;/p&gt;
&lt;p&gt;When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back
request, if another thread handle disconnect event at the same time, and
try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu
irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before
handling it.&lt;/p&gt;
&lt;p&gt;e.g.
qmu done irq on cpu0                 thread running on cpu1&lt;/p&gt;
&lt;p&gt;qmu_done_tx()
  handle gpd [0]
    mtu3_requ_complete()        mtu3_gadget_ep_disable()
      unlock @mtu-&amp;gt;lock
        give back request         lock @mtu-&amp;gt;lock
                                    mtu3_ep_disable()
                                      mtu3_gpd_ring_free()
                                   unlock @mtu-&amp;gt;lock
      lock @mtu-&amp;gt;lock
    get next gpd [1]&lt;/p&gt;
&lt;p&gt;[1]: goto [0] to handle next gpd, and next gpd may be NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-54159</guid>
    </item>
    <item>
      <title>GHSA-mgqh-xx5m-2h5f</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mgqh-xx5m-2h5f</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: mtu3: fix kernel panic at qmu transfer done irq handler&lt;/p&gt;
&lt;p&gt;When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back
request, if another thread handle disconnect event at the same time, and
try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu
irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before
handling it.&lt;/p&gt;
&lt;p&gt;e.g.
qmu done irq on cpu0                 thread running on cpu1&lt;/p&gt;
&lt;p&gt;qmu_done_tx()
  handle gpd [0]
    mtu3_requ_complete()        mtu3_gadget_ep_disable()
      unlock @mtu-&amp;gt;lock
        give back request         lock @mtu-&amp;gt;lock
                                    mtu3_ep_disable()
                                      mtu3_gpd_ring_free()
                                   unlock @mtu-&amp;gt;lock
      lock @mtu-&amp;gt;lock
    get next gpd [1]&lt;/p&gt;
&lt;p&gt;[1]: goto [0] to handle next gpd, and next gpd may be NULL.&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;usb: mtu3: fix kernel panic at qmu transfer done irq handler&lt;/p&gt;
&lt;p&gt;When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back
request, if another thread handle disconnect event at the same time, and
try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu
irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before
handling it.&lt;/p&gt;
&lt;p&gt;e.g.
qmu done irq on cpu0                 thread running on cpu1&lt;/p&gt;
&lt;p&gt;qmu_done_tx()
  handle gpd [0]
    mtu3_requ_complete()        mtu3_gadget_ep_disable()
      unlock @mtu-&amp;gt;lock
        give back request         lock @mtu-&amp;gt;lock
                                    mtu3_ep_disable()
                                      mtu3_gpd_ring_free()
                                   unlock @mtu-&amp;gt;lock
      lock @mtu-&amp;gt;lock
    get next gpd [1]&lt;/p&gt;
&lt;p&gt;[1]: goto [0] to handle next gpd, and next gpd may be NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mgqh-xx5m-2h5f</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54159</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54159</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 136 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix kernel panic at qmu transfer done irq handler When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back request, if another thread handle disconnect event at the same time, and try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before handling it. e.g. qmu done irq on cpu0                 thread running on cpu1 qmu_done_tx()   handle gpd [0]     mtu3_requ_complete()        mtu3_gadget_ep_disable()       unlock @mtu-&amp;gt;lock         give back request         lock @mtu-&amp;gt;lock                                     mtu3_ep_disable()                                       mtu3_gpd_ring_free()                                    unlock @mtu-&amp;gt;lock       lock @mtu-&amp;gt;lock     get next gpd [1] [1]: goto [0] to handle next gpd, and next gpd may be NULL.&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 136 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix kernel panic at qmu transfer done irq handler When handle qmu transfer irq, it will unlock @mtu-&amp;gt;lock before give back request, if another thread handle disconnect event at the same time, and try to disable ep, it may lock @mtu-&amp;gt;lock and free qmu ring, then qmu irq hanlder may get a NULL gpd, avoid the KE by checking gpd&amp;#39;s value before handling it. e.g. qmu done irq on cpu0                 thread running on cpu1 qmu_done_tx()   handle gpd [0]     mtu3_requ_complete()        mtu3_gadget_ep_disable()       unlock @mtu-&amp;gt;lock         give back request         lock @mtu-&amp;gt;lock                                     mtu3_ep_disable()                                       mtu3_gpd_ring_free()                                    unlock @mtu-&amp;gt;lock       lock @mtu-&amp;gt;lock     get next gpd [1] [1]: goto [0] to handle next gpd, and next gpd may be NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54159</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
