<?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>Mon, 12 Oct 2026 07:56:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39801 — usb: dwc3: Remove WARN_ON for device endpoint command timeouts</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-39801</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: Remove WARN_ON for device endpoint command timeouts&lt;/p&gt;
&lt;p&gt;This commit addresses a rarely observed endpoint command timeout
which causes kernel panic due to warn when &amp;#39;panic_on_warn&amp;#39; is enabled
and unnecessary call trace prints when &amp;#39;panic_on_warn&amp;#39; is disabled.
It is seen during fast software-controlled connect/disconnect testcases.
The following is one such endpoint command timeout that we observed:&lt;/p&gt;
&lt;p&gt;1. Connect
   =======
-&amp;gt;dwc3_thread_interrupt
 -&amp;gt;dwc3_ep0_interrupt
  -&amp;gt;configfs_composite_setup
   -&amp;gt;composite_setup
    -&amp;gt;usb_ep_queue
     -&amp;gt;dwc3_gadget_ep0_queue
      -&amp;gt;__dwc3_gadget_ep0_queue
       -&amp;gt;__dwc3_ep0_do_control_data
        -&amp;gt;dwc3_send_gadget_ep_cmd&lt;/p&gt;
&lt;p&gt;2. Disconnect
   ==========
-&amp;gt;dwc3_thread_interrupt
 -&amp;gt;dwc3_gadget_disconnect_interrupt
  -&amp;gt;dwc3_ep0_reset_state
   -&amp;gt;dwc3_ep0_end_control_data
    -&amp;gt;dwc3_send_gadget_ep_cmd&lt;/p&gt;
&lt;p&gt;In the issue scenario, in Exynos platforms, we observed that control
transfers for the previous connect have not yet been completed and end
transfer command sent as a part of the disconnect sequence and
processing of USB_ENDPOINT_HALT feature request from the host timeout.
This maybe an expected scenario since the controller is processing EP
commands sent as a part of the previous connect. It maybe better to
remove WARN_ON in all places where device endpoint commands are sent to
avoid unnecessary kernel panic due to warn.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: Remove WARN_ON for device endpoint command timeouts&lt;/p&gt;
&lt;p&gt;This commit addresses a rarely observed endpoint command timeout
which causes kernel panic due to warn when &amp;#39;panic_on_warn&amp;#39; is enabled
and unnecessary call trace prints when &amp;#39;panic_on_warn&amp;#39; is disabled.
It is seen during fast software-controlled connect/disconnect testcases.
The following is one such endpoint command timeout that we observed:&lt;/p&gt;
&lt;p&gt;1. Connect
   =======
-&amp;gt;dwc3_thread_interrupt
 -&amp;gt;dwc3_ep0_interrupt
  -&amp;gt;configfs_composite_setup
   -&amp;gt;composite_setup
    -&amp;gt;usb_ep_queue
     -&amp;gt;dwc3_gadget_ep0_queue
      -&amp;gt;__dwc3_gadget_ep0_queue
       -&amp;gt;__dwc3_ep0_do_control_data
        -&amp;gt;dwc3_send_gadget_ep_cmd&lt;/p&gt;
&lt;p&gt;2. Disconnect
   ==========
-&amp;gt;dwc3_thread_interrupt
 -&amp;gt;dwc3_gadget_disconnect_interrupt
  -&amp;gt;dwc3_ep0_reset_state
   -&amp;gt;dwc3_ep0_end_control_data
    -&amp;gt;dwc3_send_gadget_ep_cmd&lt;/p&gt;
&lt;p&gt;In the issue scenario, in Exynos platforms, we observed that control
transfers for the previous connect have not yet been completed and end
transfer command sent as a part of the disconnect sequence and
processing of USB_ENDPOINT_HALT feature request from the host timeout.
This maybe an expected scenario since the controller is processing EP
commands sent as a part of the previous connect. It maybe better to
remove WARN_ON in all places where device endpoint commands are sent to
avoid unnecessary kernel panic due to warn.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-39801</guid>
    </item>
  </channel>
</rss>
