<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 22:00:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72336</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72336</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72336</guid>
    </item>
    <item>
      <title>EUVD-2026-353745</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353745</link>
      <description>EUVD-2026-353745</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353745</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72336</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72336</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: 6lowpan: hold L2CAP conn across debugfs control&lt;/p&gt;
&lt;p&gt;get_l2cap_conn() looks up an LE hci_conn under hdev protection, but
then drops that protection before reading hcon-&amp;gt;l2cap_data and before
lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or
device close can tear down the same L2CAP connection in that window.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the order
within that path:&lt;/p&gt;
&lt;p&gt;6LoWPAN control write:              HCI disconnect/device close:
  1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches
     and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.
  2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears
     protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the
                                         L2CAP connection reference.
  3. lowpan_control_write() reads     3. hci_conn_del() removes and drops
     conn-&amp;gt;hcon.                         the HCI connection.&lt;/p&gt;
&lt;p&gt;Take a reference to the L2CAP connection with
l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that
reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the
existing L2CAP ACL receive-side handoff and keeps the connection
dereferenceable after leaving hdev protection.  Export the existing helper
so the bluetooth_6lowpan module can use the same lifetime primitive.&lt;/p&gt;
&lt;p&gt;Validation reproduced this kernel report:
BUG:…&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: 6lowpan: hold L2CAP conn across debugfs control&lt;/p&gt;
&lt;p&gt;get_l2cap_conn() looks up an LE hci_conn under hdev protection, but
then drops that protection before reading hcon-&amp;gt;l2cap_data and before
lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or
device close can tear down the same L2CAP connection in that window.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the order
within that path:&lt;/p&gt;
&lt;p&gt;6LoWPAN control write:              HCI disconnect/device close:
  1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches
     and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.
  2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears
     protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the
                                         L2CAP connection reference.
  3. lowpan_control_write() reads     3. hci_conn_del() removes and drops
     conn-&amp;gt;hcon.                         the HCI connection.&lt;/p&gt;
&lt;p&gt;Take a reference to the L2CAP connection with
l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that
reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the
existing L2CAP ACL receive-side handoff and keeps the connection
dereferenceable after leaving hdev protection.  Export the existing helper
so the bluetooth_6lowpan module can use the same lifetime primitive.&lt;/p&gt;
&lt;p&gt;Validation reproduced this kernel report:
BUG:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72336</guid>
    </item>
    <item>
      <title>GHSA-53r8-c46r-w2fg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-53r8-c46r-w2fg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: 6lowpan: hold L2CAP conn across debugfs control&lt;/p&gt;
&lt;p&gt;get_l2cap_conn() looks up an LE hci_conn under hdev protection, but
then drops that protection before reading hcon-&amp;gt;l2cap_data and before
lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or
device close can tear down the same L2CAP connection in that window.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the order
within that path:&lt;/p&gt;
&lt;p&gt;6LoWPAN control write:              HCI disconnect/device close:
  1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches
     and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.
  2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears
     protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the
                                         L2CAP connection reference.
  3. lowpan_control_write() reads     3. hci_conn_del() removes and drops
     conn-&amp;gt;hcon.                         the HCI connection.&lt;/p&gt;
&lt;p&gt;Take a reference to the L2CAP connection with
l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that
reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the
existing L2CAP ACL receive-side handoff and keeps the connection
dereferenceable after leaving hdev protection.  Export the existing helper
so the bluetooth_6lowpan module can use the same lifetime primitive.&lt;/p&gt;
&lt;p&gt;Validation reproduced this kernel report:
BUG:…&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: 6lowpan: hold L2CAP conn across debugfs control&lt;/p&gt;
&lt;p&gt;get_l2cap_conn() looks up an LE hci_conn under hdev protection, but
then drops that protection before reading hcon-&amp;gt;l2cap_data and before
lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or
device close can tear down the same L2CAP connection in that window.&lt;/p&gt;
&lt;p&gt;The buggy scenario involves two paths, with each column showing the order
within that path:&lt;/p&gt;
&lt;p&gt;6LoWPAN control write:              HCI disconnect/device close:
  1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches
     and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.
  2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears
     protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the
                                         L2CAP connection reference.
  3. lowpan_control_write() reads     3. hci_conn_del() removes and drops
     conn-&amp;gt;hcon.                         the HCI connection.&lt;/p&gt;
&lt;p&gt;Take a reference to the L2CAP connection with
l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that
reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the
existing L2CAP ACL receive-side handoff and keeps the connection
dereferenceable after leaving hdev protection.  Export the existing helper
so the bluetooth_6lowpan module can use the same lifetime primitive.&lt;/p&gt;
&lt;p&gt;Validation reproduced this kernel report:
BUG:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-53r8-c46r-w2fg</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72336</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72336</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: 6lowpan: hold L2CAP conn across debugfs control get_l2cap_conn() looks up an LE hci_conn under hdev protection, but then drops that protection before reading hcon-&amp;gt;l2cap_data and before lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or device close can tear down the same L2CAP connection in that window. The buggy scenario involves two paths, with each column showing the order within that path: 6LoWPAN control write:              HCI disconnect/device close:   1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches      and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.   2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears      protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the                                          L2CAP connection reference.   3. lowpan_control_write() reads     3. hci_conn_del() removes and drops      conn-&amp;gt;hcon.                         the HCI connection. Take a reference to the L2CAP connection with l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the existing L2CAP ACL receive-side handoff and keeps the connection dereferenceable after leaving hdev protection.  Export the existing helper so the bluetooth_6lowpan module can use the same lifetime primitive. Validation reproduced this kernel report: BUG: KASAN:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: 6lowpan: hold L2CAP conn across debugfs control get_l2cap_conn() looks up an LE hci_conn under hdev protection, but then drops that protection before reading hcon-&amp;gt;l2cap_data and before lowpan_control_write() later dereferences conn-&amp;gt;hcon.  A disconnect or device close can tear down the same L2CAP connection in that window. The buggy scenario involves two paths, with each column showing the order within that path: 6LoWPAN control write:              HCI disconnect/device close:   1. get_l2cap_conn() finds hcon      1. hci_disconn_cfm() dispatches      and hcon-&amp;gt;l2cap_data.               the L2CAP disconnect callback.   2. get_l2cap_conn() drops hdev      2. l2cap_conn_del() clears      protection and returns conn.        hcon-&amp;gt;l2cap_data and drops the                                          L2CAP connection reference.   3. lowpan_control_write() reads     3. hci_conn_del() removes and drops      conn-&amp;gt;hcon.                         the HCI connection. Take a reference to the L2CAP connection with l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that reference after the debugfs command&amp;#39;s last use of conn.  This mirrors the existing L2CAP ACL receive-side handoff and keeps the connection dereferenceable after leaving hdev protection.  Export the existing helper so the bluetooth_6lowpan module can use the same lifetime primitive. Validation reproduced this kernel report: BUG: KASAN:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72336</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
