<?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 04:55:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50833 — Bluetooth: use hdev-&gt;workqueue when queuing hdev-&gt;{cmd,ncmd}_timer works</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50833</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: use hdev-&amp;gt;workqueue when queuing hdev-&amp;gt;{cmd,ncmd}_timer works&lt;/p&gt;
&lt;p&gt;syzbot is reporting attempt to schedule hdev-&amp;gt;cmd_work work from system_wq
WQ into hdev-&amp;gt;workqueue WQ which is under draining operation [1], for
commit c8efcc2589464ac7 (&amp;#34;workqueue: allow chained queueing during
destruction&amp;#34;) does not allow such operation.&lt;/p&gt;
&lt;p&gt;The check introduced by commit 877afadad2dce8aa (&amp;#34;Bluetooth: When HCI work
queue is drained, only queue chained work&amp;#34;) was incomplete.&lt;/p&gt;
&lt;p&gt;Use hdev-&amp;gt;workqueue WQ when queuing hdev-&amp;gt;{cmd,ncmd}_timer works because
hci_{cmd,ncmd}_timeout() calls queue_work(hdev-&amp;gt;workqueue). Also, protect
the queuing operation with RCU read lock in order to avoid calling
queue_delayed_work() after cancel_delayed_work() completed.&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: use hdev-&amp;gt;workqueue when queuing hdev-&amp;gt;{cmd,ncmd}_timer works&lt;/p&gt;
&lt;p&gt;syzbot is reporting attempt to schedule hdev-&amp;gt;cmd_work work from system_wq
WQ into hdev-&amp;gt;workqueue WQ which is under draining operation [1], for
commit c8efcc2589464ac7 (&amp;#34;workqueue: allow chained queueing during
destruction&amp;#34;) does not allow such operation.&lt;/p&gt;
&lt;p&gt;The check introduced by commit 877afadad2dce8aa (&amp;#34;Bluetooth: When HCI work
queue is drained, only queue chained work&amp;#34;) was incomplete.&lt;/p&gt;
&lt;p&gt;Use hdev-&amp;gt;workqueue WQ when queuing hdev-&amp;gt;{cmd,ncmd}_timer works because
hci_{cmd,ncmd}_timeout() calls queue_work(hdev-&amp;gt;workqueue). Also, protect
the queuing operation with RCU read lock in order to avoid calling
queue_delayed_work() after cancel_delayed_work() completed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50833</guid>
    </item>
  </channel>
</rss>
