<?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 00:25:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49309 — drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49309</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;drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()&lt;/p&gt;
&lt;p&gt;There is a deadlock in rtw_surveydone_event_callback(),
which is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)                  |      (Thread 2)
                               | _set_timer()
rtw_surveydone_event_callback()|  mod_timer()
 spin_lock_bh() //(1)          |  (wait a time)
 ...                           | rtw_scan_timeout_handler()
 del_timer_sync()              |  spin_lock_bh() //(2)
 (wait timer to stop)          |  ...&lt;/p&gt;
&lt;p&gt;We hold pmlmepriv-&amp;gt;lock in position (1) of thread 1 and use
del_timer_sync() to wait timer to stop, but timer handler
also need pmlmepriv-&amp;gt;lock in position (2) of thread 2.
As a result, rtw_surveydone_event_callback() will block forever.&lt;/p&gt;
&lt;p&gt;This patch extracts del_timer_sync() from the protection of
spin_lock_bh(), which could let timer handler to obtain
the needed lock. What`s more, we change spin_lock_bh() in
rtw_scan_timeout_handler() to spin_lock_irq(). Otherwise,
spin_lock_bh() will also cause deadlock() in timer handler.&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;drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()&lt;/p&gt;
&lt;p&gt;There is a deadlock in rtw_surveydone_event_callback(),
which is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)                  |      (Thread 2)
                               | _set_timer()
rtw_surveydone_event_callback()|  mod_timer()
 spin_lock_bh() //(1)          |  (wait a time)
 ...                           | rtw_scan_timeout_handler()
 del_timer_sync()              |  spin_lock_bh() //(2)
 (wait timer to stop)          |  ...&lt;/p&gt;
&lt;p&gt;We hold pmlmepriv-&amp;gt;lock in position (1) of thread 1 and use
del_timer_sync() to wait timer to stop, but timer handler
also need pmlmepriv-&amp;gt;lock in position (2) of thread 2.
As a result, rtw_surveydone_event_callback() will block forever.&lt;/p&gt;
&lt;p&gt;This patch extracts del_timer_sync() from the protection of
spin_lock_bh(), which could let timer handler to obtain
the needed lock. What`s more, we change spin_lock_bh() in
rtw_scan_timeout_handler() to spin_lock_irq(). Otherwise,
spin_lock_bh() will also cause deadlock() in timer handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49309</guid>
    </item>
  </channel>
</rss>
