<?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, 09 Oct 2026 21:51:11 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98246</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-98246</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://vulnerability.circl.lu/vuln/bell-cve-2026-98246</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98246</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98246</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Serialize local codec list cleanup&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock.
Codec list additions and both traversals in sco_sock_getsockopt() use that
lock, but the close path does not. A close and BT_CODEC query can therefore
interleave as follows:&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync()          sco_sock_getsockopt()
                                hci_dev_lock()
                                fetch codec entry
  hci_codec_list_clear()
    kfree(entry)
                                read entry-&amp;gt;id&lt;/p&gt;
&lt;p&gt;The reader then accesses an entry which the close path has freed. KASAN&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0
  Read of size 1 at addr ffff8881001c3450
  Call Trace:
   sco_sock_getsockopt+0xfa0/0xfe0
   do_sock_getsockopt+0x537/0x7b0
   __sys_getsockopt+0xf2/0x170
  Allocated by task 92:
   hci_codec_list_add.isra.0+0x2c/0x440
   hci_read_codec_capabilities+0x224/0x590
   hci_read_supported_codecs+0x2c2/0x640
  Freed by task 92:
   kfree+0x131/0x3c0
   hci_codec_list_clear+0xd8/0x160
   hci_dev_close_sync+0x92a/0xfa0&lt;/p&gt;
&lt;p&gt;Take hdev-&amp;gt;lock around the clear operation at its existing point in the
close path. This makes the clear wait for active readers and prevents a new
traversal until the list is empty without changing teardown ordering.&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_sync: Serialize local codec list cleanup&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock.
Codec list additions and both traversals in sco_sock_getsockopt() use that
lock, but the close path does not. A close and BT_CODEC query can therefore
interleave as follows:&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync()          sco_sock_getsockopt()
                                hci_dev_lock()
                                fetch codec entry
  hci_codec_list_clear()
    kfree(entry)
                                read entry-&amp;gt;id&lt;/p&gt;
&lt;p&gt;The reader then accesses an entry which the close path has freed. KASAN&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0
  Read of size 1 at addr ffff8881001c3450
  Call Trace:
   sco_sock_getsockopt+0xfa0/0xfe0
   do_sock_getsockopt+0x537/0x7b0
   __sys_getsockopt+0xf2/0x170
  Allocated by task 92:
   hci_codec_list_add.isra.0+0x2c/0x440
   hci_read_codec_capabilities+0x224/0x590
   hci_read_supported_codecs+0x2c2/0x640
  Freed by task 92:
   kfree+0x131/0x3c0
   hci_codec_list_clear+0xd8/0x160
   hci_dev_close_sync+0x92a/0xfa0&lt;/p&gt;
&lt;p&gt;Take hdev-&amp;gt;lock around the clear operation at its existing point in the
close path. This makes the clear wait for active readers and prevents a new
traversal until the list is empty without changing teardown ordering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98246</guid>
    </item>
    <item>
      <title>GHSA-4jxq-xw37-v6h5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-4jxq-xw37-v6h5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Serialize local codec list cleanup&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock.
Codec list additions and both traversals in sco_sock_getsockopt() use that
lock, but the close path does not. A close and BT_CODEC query can therefore
interleave as follows:&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync()          sco_sock_getsockopt()
                                hci_dev_lock()
                                fetch codec entry
  hci_codec_list_clear()
    kfree(entry)
                                read entry-&amp;gt;id&lt;/p&gt;
&lt;p&gt;The reader then accesses an entry which the close path has freed. KASAN&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0
  Read of size 1 at addr ffff8881001c3450
  Call Trace:
   sco_sock_getsockopt+0xfa0/0xfe0
   do_sock_getsockopt+0x537/0x7b0
   __sys_getsockopt+0xf2/0x170
  Allocated by task 92:
   hci_codec_list_add.isra.0+0x2c/0x440
   hci_read_codec_capabilities+0x224/0x590
   hci_read_supported_codecs+0x2c2/0x640
  Freed by task 92:
   kfree+0x131/0x3c0
   hci_codec_list_clear+0xd8/0x160
   hci_dev_close_sync+0x92a/0xfa0&lt;/p&gt;
&lt;p&gt;Take hdev-&amp;gt;lock around the clear operation at its existing point in the
close path. This makes the clear wait for active readers and prevents a new
traversal until the list is empty without changing teardown ordering.&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_sync: Serialize local codec list cleanup&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock.
Codec list additions and both traversals in sco_sock_getsockopt() use that
lock, but the close path does not. A close and BT_CODEC query can therefore
interleave as follows:&lt;/p&gt;
&lt;p&gt;hci_dev_close_sync()          sco_sock_getsockopt()
                                hci_dev_lock()
                                fetch codec entry
  hci_codec_list_clear()
    kfree(entry)
                                read entry-&amp;gt;id&lt;/p&gt;
&lt;p&gt;The reader then accesses an entry which the close path has freed. KASAN&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0
  Read of size 1 at addr ffff8881001c3450
  Call Trace:
   sco_sock_getsockopt+0xfa0/0xfe0
   do_sock_getsockopt+0x537/0x7b0
   __sys_getsockopt+0xf2/0x170
  Allocated by task 92:
   hci_codec_list_add.isra.0+0x2c/0x440
   hci_read_codec_capabilities+0x224/0x590
   hci_read_supported_codecs+0x2c2/0x640
  Freed by task 92:
   kfree+0x131/0x3c0
   hci_codec_list_clear+0xd8/0x160
   hci_dev_close_sync+0x92a/0xfa0&lt;/p&gt;
&lt;p&gt;Take hdev-&amp;gt;lock around the clear operation at its existing point in the
close path. This makes the clear wait for active readers and prevents a new
traversal until the list is empty without changing teardown ordering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-4jxq-xw37-v6h5</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98246 — Bluetooth: hci_sync: Serialize local codec list cleanup</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-98246</link>
      <description>msrc_CVE-2026-98246</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-98246</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98246</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98246</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: hci_sync: Serialize local codec list cleanup hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock. Codec list additions and both traversals in sco_sock_getsockopt() use that lock, but the close path does not. A close and BT_CODEC query can therefore interleave as follows:   hci_dev_close_sync()          sco_sock_getsockopt()                                 hci_dev_lock()                                 fetch codec entry   hci_codec_list_clear()     kfree(entry)                                 read entry-&amp;gt;id The reader then accesses an entry which the close path has freed. KASAN   BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0   Read of size 1 at addr ffff8881001c3450   Call Trace:    sco_sock_getsockopt+0xfa0/0xfe0    do_sock_getsockopt+0x537/0x7b0    __sys_getsockopt+0xf2/0x170   Allocated by task 92:    hci_codec_list_add.isra.0+0x2c/0x440    hci_read_codec_capabilities+0x224/0x590    hci_read_supported_codecs+0x2c2/0x640   Freed by task 92:    kfree+0x131/0x3c0    hci_codec_list_clear+0xd8/0x160    hci_dev_close_sync+0x92a/0xfa0 Take hdev-&amp;gt;lock around the clear operation at its existing point in the close path. This makes the clear wait for active readers and prevents a new traversal until the list is empty without changing teardown ordering.&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: hci_sync: Serialize local codec list cleanup hci_dev_close_sync() clears hdev-&amp;gt;local_codecs after releasing hdev-&amp;gt;lock. Codec list additions and both traversals in sco_sock_getsockopt() use that lock, but the close path does not. A close and BT_CODEC query can therefore interleave as follows:   hci_dev_close_sync()          sco_sock_getsockopt()                                 hci_dev_lock()                                 fetch codec entry   hci_codec_list_clear()     kfree(entry)                                 read entry-&amp;gt;id The reader then accesses an entry which the close path has freed. KASAN   BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0   Read of size 1 at addr ffff8881001c3450   Call Trace:    sco_sock_getsockopt+0xfa0/0xfe0    do_sock_getsockopt+0x537/0x7b0    __sys_getsockopt+0xf2/0x170   Allocated by task 92:    hci_codec_list_add.isra.0+0x2c/0x440    hci_read_codec_capabilities+0x224/0x590    hci_read_supported_codecs+0x2c2/0x640   Freed by task 92:    kfree+0x131/0x3c0    hci_codec_list_clear+0xd8/0x160    hci_dev_close_sync+0x92a/0xfa0 Take hdev-&amp;gt;lock around the clear operation at its existing point in the close path. This makes the clear wait for active readers and prevents a new traversal until the list is empty without changing teardown ordering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98246</guid>
    </item>
  </channel>
</rss>
