<?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>Mon, 28 Sep 2026 15:18:52 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97975</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97975</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()&lt;/p&gt;
&lt;p&gt;A NULL pointer dereference in klist_put() occurs when a child device (such
as a BNEP network device in bnep_session) is concurrently being
unregistered while hci_conn_del_sysfs() reparents child devices.&lt;/p&gt;
&lt;p&gt;This is caused by a race condition between hci_conn_del_sysfs() and
concurrent child device unregistration (e.g. bnep_session calling
unregister_netdev()). During device unregistration, device_del() snapshots
a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the
child device using device_find_any_child() and calls device_move() to
reparent it to NULL, which removes the node from its parent&amp;#39;s klist and
clears knode_parent. Subsequently, device_del() calls
klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing
klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node,
resulting in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix
use-after-free in device_for_each_child()&amp;#34;), which replaced
device_find_child(..., __match_tty) with device_find_any_child() in
hci_conn_del_sysfs(). That change was intended to avoid a use-after-free
where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held
references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to
hdev-&amp;gt;dev while registered in sysfs.&lt;/p&gt;
&lt;p&gt;Fix the issue properly by taking an explicit re…&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: hci_sysfs: Fix NULL pointer dereference in device_del()&lt;/p&gt;
&lt;p&gt;A NULL pointer dereference in klist_put() occurs when a child device (such
as a BNEP network device in bnep_session) is concurrently being
unregistered while hci_conn_del_sysfs() reparents child devices.&lt;/p&gt;
&lt;p&gt;This is caused by a race condition between hci_conn_del_sysfs() and
concurrent child device unregistration (e.g. bnep_session calling
unregister_netdev()). During device unregistration, device_del() snapshots
a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the
child device using device_find_any_child() and calls device_move() to
reparent it to NULL, which removes the node from its parent&amp;#39;s klist and
clears knode_parent. Subsequently, device_del() calls
klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing
klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node,
resulting in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix
use-after-free in device_for_each_child()&amp;#34;), which replaced
device_find_child(..., __match_tty) with device_find_any_child() in
hci_conn_del_sysfs(). That change was intended to avoid a use-after-free
where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held
references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to
hdev-&amp;gt;dev while registered in sysfs.&lt;/p&gt;
&lt;p&gt;Fix the issue properly by taking an explicit re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97975</guid>
    </item>
    <item>
      <title>GHSA-2vfm-8xc8-7w2c</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2vfm-8xc8-7w2c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()&lt;/p&gt;
&lt;p&gt;A NULL pointer dereference in klist_put() occurs when a child device (such
as a BNEP network device in bnep_session) is concurrently being
unregistered while hci_conn_del_sysfs() reparents child devices.&lt;/p&gt;
&lt;p&gt;This is caused by a race condition between hci_conn_del_sysfs() and
concurrent child device unregistration (e.g. bnep_session calling
unregister_netdev()). During device unregistration, device_del() snapshots
a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the
child device using device_find_any_child() and calls device_move() to
reparent it to NULL, which removes the node from its parent&amp;#39;s klist and
clears knode_parent. Subsequently, device_del() calls
klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing
klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node,
resulting in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix
use-after-free in device_for_each_child()&amp;#34;), which replaced
device_find_child(..., __match_tty) with device_find_any_child() in
hci_conn_del_sysfs(). That change was intended to avoid a use-after-free
where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held
references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to
hdev-&amp;gt;dev while registered in sysfs.&lt;/p&gt;
&lt;p&gt;Fix the issue properly by taking an explicit re…&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: hci_sysfs: Fix NULL pointer dereference in device_del()&lt;/p&gt;
&lt;p&gt;A NULL pointer dereference in klist_put() occurs when a child device (such
as a BNEP network device in bnep_session) is concurrently being
unregistered while hci_conn_del_sysfs() reparents child devices.&lt;/p&gt;
&lt;p&gt;This is caused by a race condition between hci_conn_del_sysfs() and
concurrent child device unregistration (e.g. bnep_session calling
unregister_netdev()). During device unregistration, device_del() snapshots
a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the
child device using device_find_any_child() and calls device_move() to
reparent it to NULL, which removes the node from its parent&amp;#39;s klist and
clears knode_parent. Subsequently, device_del() calls
klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing
klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node,
resulting in a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix
use-after-free in device_for_each_child()&amp;#34;), which replaced
device_find_child(..., __match_tty) with device_find_any_child() in
hci_conn_del_sysfs(). That change was intended to avoid a use-after-free
where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held
references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to
hdev-&amp;gt;dev while registered in sysfs.&lt;/p&gt;
&lt;p&gt;Fix the issue properly by taking an explicit re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2vfm-8xc8-7w2c</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97975</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97975</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() A NULL pointer dereference in klist_put() occurs when a child device (such as a BNEP network device in bnep_session) is concurrently being unregistered while hci_conn_del_sysfs() reparents child devices. This is caused by a race condition between hci_conn_del_sysfs() and concurrent child device unregistration (e.g. bnep_session calling unregister_netdev()). During device unregistration, device_del() snapshots a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the child device using device_find_any_child() and calls device_move() to reparent it to NULL, which removes the node from its parent&amp;#39;s klist and clears knode_parent. Subsequently, device_del() calls klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node, resulting in a NULL pointer dereference. This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix use-after-free in device_for_each_child()&amp;#34;), which replaced device_find_child(..., __match_tty) with device_find_any_child() in hci_conn_del_sysfs(). That change was intended to avoid a use-after-free where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to hdev-&amp;gt;dev while registered in sysfs. Fix the issue properly by taking an explicit referen…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() A NULL pointer dereference in klist_put() occurs when a child device (such as a BNEP network device in bnep_session) is concurrently being unregistered while hci_conn_del_sysfs() reparents child devices. This is caused by a race condition between hci_conn_del_sysfs() and concurrent child device unregistration (e.g. bnep_session calling unregister_netdev()). During device unregistration, device_del() snapshots a non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the child device using device_find_any_child() and calls device_move() to reparent it to NULL, which removes the node from its parent&amp;#39;s klist and clears knode_parent. Subsequently, device_del() calls klist_del(&amp;amp;dev-&amp;gt;p-&amp;gt;knode_parent) using the stale parent snapshot, causing klist_put() to dereference knode_klist(n)-&amp;gt;put on an already removed node, resulting in a NULL pointer dereference. This race was introduced by commit 27aabf27fd01 (&amp;#34;Bluetooth: fix use-after-free in device_for_each_child()&amp;#34;), which replaced device_find_child(..., __match_tty) with device_find_any_child() in hci_conn_del_sysfs(). That change was intended to avoid a use-after-free where conn-&amp;gt;dev outlived its parent hdev-&amp;gt;dev when child devices held references to conn-&amp;gt;dev, because conn-&amp;gt;dev only held a reference to hdev-&amp;gt;dev while registered in sysfs. Fix the issue properly by taking an explicit referen…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97975</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
