<?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>Fri, 02 Oct 2026 22:49:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90256</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90256</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90256</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90256</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind&lt;/p&gt;
&lt;p&gt;hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt;
l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted
concurrently.&lt;/p&gt;
&lt;p&gt;disc_work is disabled sync in hci_conn_del(), so we cannot take
hci_dev_lock in disc_work.&lt;/p&gt;
&lt;p&gt;Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock
which is held in other access paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind&lt;/p&gt;
&lt;p&gt;hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt;
l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted
concurrently.&lt;/p&gt;
&lt;p&gt;disc_work is disabled sync in hci_conn_del(), so we cannot take
hci_dev_lock in disc_work.&lt;/p&gt;
&lt;p&gt;Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock
which is held in other access paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90256</guid>
    </item>
    <item>
      <title>GHSA-323m-rj3w-9jqp</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-323m-rj3w-9jqp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind&lt;/p&gt;
&lt;p&gt;hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt;
l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted
concurrently.&lt;/p&gt;
&lt;p&gt;disc_work is disabled sync in hci_conn_del(), so we cannot take
hci_dev_lock in disc_work.&lt;/p&gt;
&lt;p&gt;Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock
which is held in other access paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind&lt;/p&gt;
&lt;p&gt;hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt;
l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted
concurrently.&lt;/p&gt;
&lt;p&gt;disc_work is disabled sync in hci_conn_del(), so we cannot take
hci_dev_lock in disc_work.&lt;/p&gt;
&lt;p&gt;Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock
which is held in other access paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-323m-rj3w-9jqp</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90256</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90256</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt; l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted concurrently. disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work. Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock which is held in other access paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -&amp;gt; hci_proto_disconn_ind -&amp;gt; l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted concurrently. disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work. Fix by using proto_lock to guard l2cap_data, in addition to hdev-&amp;gt;lock which is held in other access paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90256</guid>
    </item>
  </channel>
</rss>
