<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T17:31:41.695836+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-54210</id>
    <title>CVE-2023-54210 — Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()</title>
    <updated>2026-09-30T17:31:41.756280+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()</p>
<p>KASAN reports that there'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() -&gt;
  msft_remove_monitor() -&gt;
  msft_remove_monitor_sync() -&gt;
  msft_le_cancel_monitor_advertisement_cb() -&gt;
  hci_free_adv_monitor()</p>
<p>Let's fix the problem by just stashing the relevant data when it's
still valid.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-54210"/>
  </entry>
</feed>
