<?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>Tue, 29 Sep 2026 05:29:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50202 — PM: hibernate: defer device probing when resuming from hibernation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50202</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;PM: hibernate: defer device probing when resuming from hibernation&lt;/p&gt;
&lt;p&gt;syzbot is reporting hung task at misc_open() [1], for there is a race
window of AB-BA deadlock which involves probe_count variable. Currently
wait_for_device_probe() from snapshot_open() from misc_open() can sleep
forever with misc_mtx held if probe_count cannot become 0.&lt;/p&gt;
&lt;p&gt;When a device is probed by hub_event() work function, probe_count is
incremented before the probe function starts, and probe_count is
decremented after the probe function completed.&lt;/p&gt;
&lt;p&gt;There are three cases that can prevent probe_count from dropping to 0.&lt;/p&gt;
&lt;p&gt;(a) A device being probed stopped responding (i.e. broken/malicious
      hardware).&lt;/p&gt;
&lt;p&gt;(b) A process emulating a USB device using /dev/raw-gadget interface
      stopped responding for some reason.&lt;/p&gt;
&lt;p&gt;(c) New device probe requests keeps coming in before existing device
      probe requests complete.&lt;/p&gt;
&lt;p&gt;The phenomenon syzbot is reporting is (b). A process which is holding
system_transition_mutex and misc_mtx is waiting for probe_count to become
0 inside wait_for_device_probe(), but the probe function which is called
 from hub_event() work function is waiting for the processes which are
blocked at mutex_lock(&amp;amp;misc_mtx) to respond via /dev/raw-gadget interface.&lt;/p&gt;
&lt;p&gt;This patch mitigates (b) by deferring wait_for_device_probe() from
snapshot_open() to snapshot_write() and snapshot_ioctl(). Please note that
the possibility of (b)…&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;PM: hibernate: defer device probing when resuming from hibernation&lt;/p&gt;
&lt;p&gt;syzbot is reporting hung task at misc_open() [1], for there is a race
window of AB-BA deadlock which involves probe_count variable. Currently
wait_for_device_probe() from snapshot_open() from misc_open() can sleep
forever with misc_mtx held if probe_count cannot become 0.&lt;/p&gt;
&lt;p&gt;When a device is probed by hub_event() work function, probe_count is
incremented before the probe function starts, and probe_count is
decremented after the probe function completed.&lt;/p&gt;
&lt;p&gt;There are three cases that can prevent probe_count from dropping to 0.&lt;/p&gt;
&lt;p&gt;(a) A device being probed stopped responding (i.e. broken/malicious
      hardware).&lt;/p&gt;
&lt;p&gt;(b) A process emulating a USB device using /dev/raw-gadget interface
      stopped responding for some reason.&lt;/p&gt;
&lt;p&gt;(c) New device probe requests keeps coming in before existing device
      probe requests complete.&lt;/p&gt;
&lt;p&gt;The phenomenon syzbot is reporting is (b). A process which is holding
system_transition_mutex and misc_mtx is waiting for probe_count to become
0 inside wait_for_device_probe(), but the probe function which is called
 from hub_event() work function is waiting for the processes which are
blocked at mutex_lock(&amp;amp;misc_mtx) to respond via /dev/raw-gadget interface.&lt;/p&gt;
&lt;p&gt;This patch mitigates (b) by deferring wait_for_device_probe() from
snapshot_open() to snapshot_write() and snapshot_ioctl(). Please note that
the possibility of (b)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50202</guid>
    </item>
  </channel>
</rss>
