<?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-29T12:07:55.345486+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-2026-23461</id>
    <title>CVE-2026-23461 — Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user</title>
    <updated>2026-09-29T12:07:55.432855+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: L2CAP: Fix use-after-free in l2cap_unregister_user</p>
<p>After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in
hci_chan_del"), l2cap_conn_del() uses conn-&gt;lock to protect access to
conn-&gt;users. However, l2cap_register_user() and l2cap_unregister_user()
don't use conn-&gt;lock, creating a race condition where these functions can
access conn-&gt;users and conn-&gt;hchan concurrently with l2cap_conn_del().</p>
<p>This can lead to use-after-free and list corruption bugs, as reported
by syzbot.</p>
<p>Fix this by changing l2cap_register_user() and l2cap_unregister_user()
to use conn-&gt;lock instead of hci_dev_lock(), ensuring consistent locking
for the l2cap_conn structure.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-23461"/>
  </entry>
</feed>
