<?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>Sun, 04 Oct 2026 18:30:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26934 — USB: core: Fix deadlock in usb_deauthorize_interface()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26934</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;USB: core: Fix deadlock in usb_deauthorize_interface()&lt;/p&gt;
&lt;p&gt;Among the attribute file callback routines in
drivers/usb/core/sysfs.c, the interface_authorized_store() function is
the only one which acquires a device lock on an ancestor device: It
calls usb_deauthorize_interface(), which locks the interface&amp;#39;s parent
USB device.&lt;/p&gt;
&lt;p&gt;The will lead to deadlock if another process already owns that lock
and tries to remove the interface, whether through a configuration
change or because the device has been disconnected.  As part of the
removal procedure, device_del() waits for all ongoing sysfs attribute
callbacks to complete.  But usb_deauthorize_interface() can&amp;#39;t complete
until the device lock has been released, and the lock won&amp;#39;t be
released until the removal has finished.&lt;/p&gt;
&lt;p&gt;The mechanism provided by sysfs to prevent this kind of deadlock is
to use the sysfs_break_active_protection() function, which tells sysfs
not to wait for the attribute callback.&lt;/p&gt;
&lt;p&gt;Reported-and-tested by: Yue Sun &amp;lt;samsun1006219@gmail.com&amp;gt;
Reported by: xingwei lee &amp;lt;xrivendell7@gmail.com&amp;gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;USB: core: Fix deadlock in usb_deauthorize_interface()&lt;/p&gt;
&lt;p&gt;Among the attribute file callback routines in
drivers/usb/core/sysfs.c, the interface_authorized_store() function is
the only one which acquires a device lock on an ancestor device: It
calls usb_deauthorize_interface(), which locks the interface&amp;#39;s parent
USB device.&lt;/p&gt;
&lt;p&gt;The will lead to deadlock if another process already owns that lock
and tries to remove the interface, whether through a configuration
change or because the device has been disconnected.  As part of the
removal procedure, device_del() waits for all ongoing sysfs attribute
callbacks to complete.  But usb_deauthorize_interface() can&amp;#39;t complete
until the device lock has been released, and the lock won&amp;#39;t be
released until the removal has finished.&lt;/p&gt;
&lt;p&gt;The mechanism provided by sysfs to prevent this kind of deadlock is
to use the sysfs_break_active_protection() function, which tells sysfs
not to wait for the attribute callback.&lt;/p&gt;
&lt;p&gt;Reported-and-tested by: Yue Sun &amp;lt;samsun1006219@gmail.com&amp;gt;
Reported by: xingwei lee &amp;lt;xrivendell7@gmail.com&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26934</guid>
    </item>
  </channel>
</rss>
