<?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>Mon, 28 Sep 2026 06:39:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41063 — Bluetooth: hci_core: cancel all works upon hci_unregister_dev()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-41063</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;Bluetooth: hci_core: cancel all works upon hci_unregister_dev()&lt;/p&gt;
&lt;p&gt;syzbot is reporting that calling hci_release_dev() from hci_error_reset()
due to hci_dev_put() from hci_error_reset() can cause deadlock at
destroy_workqueue(), for hci_error_reset() is called from
hdev-&amp;gt;req_workqueue which destroy_workqueue() needs to flush.&lt;/p&gt;
&lt;p&gt;We need to make sure that hdev-&amp;gt;{rx_work,cmd_work,tx_work} which are
queued into hdev-&amp;gt;workqueue and hdev-&amp;gt;{power_on,error_reset} which are
queued into hdev-&amp;gt;req_workqueue are no longer running by the moment&lt;/p&gt;
&lt;p&gt;destroy_workqueue(hdev-&amp;gt;workqueue);
       destroy_workqueue(hdev-&amp;gt;req_workqueue);&lt;/p&gt;
&lt;p&gt;are called from hci_release_dev().&lt;/p&gt;
&lt;p&gt;Call cancel_work_sync() on these work items from hci_unregister_dev()
as soon as hdev-&amp;gt;list is removed from hci_dev_list.&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;Bluetooth: hci_core: cancel all works upon hci_unregister_dev()&lt;/p&gt;
&lt;p&gt;syzbot is reporting that calling hci_release_dev() from hci_error_reset()
due to hci_dev_put() from hci_error_reset() can cause deadlock at
destroy_workqueue(), for hci_error_reset() is called from
hdev-&amp;gt;req_workqueue which destroy_workqueue() needs to flush.&lt;/p&gt;
&lt;p&gt;We need to make sure that hdev-&amp;gt;{rx_work,cmd_work,tx_work} which are
queued into hdev-&amp;gt;workqueue and hdev-&amp;gt;{power_on,error_reset} which are
queued into hdev-&amp;gt;req_workqueue are no longer running by the moment&lt;/p&gt;
&lt;p&gt;destroy_workqueue(hdev-&amp;gt;workqueue);
       destroy_workqueue(hdev-&amp;gt;req_workqueue);&lt;/p&gt;
&lt;p&gt;are called from hci_release_dev().&lt;/p&gt;
&lt;p&gt;Call cancel_work_sync() on these work items from hci_unregister_dev()
as soon as hdev-&amp;gt;list is removed from hci_dev_list.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-41063</guid>
    </item>
  </channel>
</rss>
