<?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-29T13:03:42.947865+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-90256</id>
    <title>CVE-2026-90256 — Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind</title>
    <updated>2026-09-29T13:03:42.966778+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: use proto_lock for l2cap_data to fix l2cap_disconn_ind</p>
<p>hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
hci_conn_timeout (disc_work) -&gt; hci_proto_disconn_ind -&gt;
l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted
concurrently.</p>
<p>disc_work is disabled sync in hci_conn_del(), so we cannot take
hci_dev_lock in disc_work.</p>
<p>Fix by using proto_lock to guard l2cap_data, in addition to hdev-&gt;lock
which is held in other access paths.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-90256"/>
  </entry>
</feed>
