<?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>Wed, 30 Sep 2026 10:29:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54210 — Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54210</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_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&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_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54210</guid>
    </item>
  </channel>
</rss>
