<?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, 10 Oct 2026 05:52:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26715 — usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26715</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend&lt;/p&gt;
&lt;p&gt;In current scenario if Plug-out and Plug-In performed continuously
there could be a chance while checking for dwc-&amp;gt;gadget_driver in
dwc3_gadget_suspend, a NULL pointer dereference may occur.&lt;/p&gt;
&lt;p&gt;Call Stack:&lt;/p&gt;
&lt;p&gt;CPU1:                           CPU2:
	gadget_unbind_driver            dwc3_suspend_common
	dwc3_gadget_stop                dwc3_gadget_suspend
                                        dwc3_disconnect_gadget&lt;/p&gt;
&lt;p&gt;CPU1 basically clears the variable and CPU2 checks the variable.
Consider CPU1 is running and right before gadget_driver is cleared
and in parallel CPU2 executes dwc3_gadget_suspend where it finds
dwc-&amp;gt;gadget_driver which is not NULL and resumes execution and then
CPU1 completes execution. CPU2 executes dwc3_disconnect_gadget where
it checks dwc-&amp;gt;gadget_driver is already NULL because of which the
NULL pointer deference occur.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend&lt;/p&gt;
&lt;p&gt;In current scenario if Plug-out and Plug-In performed continuously
there could be a chance while checking for dwc-&amp;gt;gadget_driver in
dwc3_gadget_suspend, a NULL pointer dereference may occur.&lt;/p&gt;
&lt;p&gt;Call Stack:&lt;/p&gt;
&lt;p&gt;CPU1:                           CPU2:
	gadget_unbind_driver            dwc3_suspend_common
	dwc3_gadget_stop                dwc3_gadget_suspend
                                        dwc3_disconnect_gadget&lt;/p&gt;
&lt;p&gt;CPU1 basically clears the variable and CPU2 checks the variable.
Consider CPU1 is running and right before gadget_driver is cleared
and in parallel CPU2 executes dwc3_gadget_suspend where it finds
dwc-&amp;gt;gadget_driver which is not NULL and resumes execution and then
CPU1 completes execution. CPU2 executes dwc3_disconnect_gadget where
it checks dwc-&amp;gt;gadget_driver is already NULL because of which the
NULL pointer deference occur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26715</guid>
    </item>
  </channel>
</rss>
