<?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>Sat, 03 Oct 2026 12:12:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23188 — net: usb: r8152: fix resume reset deadlock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23188</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;net: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&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;net: usb: r8152: fix resume reset deadlock&lt;/p&gt;
&lt;p&gt;rtl8152 can trigger device reset during reset which
potentially can result in a deadlock:&lt;/p&gt;
&lt;p&gt;**** DPM device timeout after 10 seconds; 15 seconds until panic ****
 Call Trace:
 &amp;lt;TASK&amp;gt;
 schedule+0x483/0x1370
 schedule_preempt_disabled+0x15/0x30
 __mutex_lock_common+0x1fd/0x470
 __rtl8152_set_mac_address+0x80/0x1f0
 dev_set_mac_address+0x7f/0x150
 rtl8152_post_reset+0x72/0x150
 usb_reset_device+0x1d0/0x220
 rtl8152_resume+0x99/0xc0
 usb_resume_interface+0x3e/0xc0
 usb_resume_both+0x104/0x150
 usb_resume+0x22/0x110&lt;/p&gt;
&lt;p&gt;The problem is that rtl8152 resume calls reset under
tp-&amp;gt;control mutex while reset basically re-enters rtl8152
and attempts to acquire the same tp-&amp;gt;control lock once
again.&lt;/p&gt;
&lt;p&gt;Reset INACCESSIBLE device outside of tp-&amp;gt;control mutex
scope to avoid recursive mutex_lock() deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23188</guid>
    </item>
  </channel>
</rss>
