<?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://db.gcve.eu</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>Tue, 03 Nov 2026 02:26:17 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98737</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98737</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Fix inquiry cache use-after-free&lt;/p&gt;
&lt;p&gt;The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates
and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and
hci_stop_discovery_sync() look up entries and read their fields without
taking hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire
hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads
the freed entry while preparing a create-connection or remote-name-cancel
command. The list traversal also races with cache updates and removal.&lt;/p&gt;
&lt;p&gt;KASAN reported these accesses:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_acl_create_conn_sync+0x5f1/0x650
   hci_cmd_sync_work+0x13c/0x290&lt;/p&gt;
&lt;p&gt;Allocated by task 90:
   hci_inquiry_cache_update+0x3e6/0x7d0
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 93:
   hci_inquiry_cache_flush+0x111/0x2b0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x269/0x5f0&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_stop_discovery_sync+0x3b1/0x3c0
   hci_cmd_sync_work+0x173/0x300&lt;/p&gt;
&lt;p&gt;Allocated by task 86:
   hci_inquiry_cache_update+0x483/0x940
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 91:
   hci_inquiry_cache_flush+0x13e/0x2f0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x26…&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: Fix inquiry cache use-after-free&lt;/p&gt;
&lt;p&gt;The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates
and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and
hci_stop_discovery_sync() look up entries and read their fields without
taking hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire
hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads
the freed entry while preparing a create-connection or remote-name-cancel
command. The list traversal also races with cache updates and removal.&lt;/p&gt;
&lt;p&gt;KASAN reported these accesses:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_acl_create_conn_sync+0x5f1/0x650
   hci_cmd_sync_work+0x13c/0x290&lt;/p&gt;
&lt;p&gt;Allocated by task 90:
   hci_inquiry_cache_update+0x3e6/0x7d0
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 93:
   hci_inquiry_cache_flush+0x111/0x2b0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x269/0x5f0&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_stop_discovery_sync+0x3b1/0x3c0
   hci_cmd_sync_work+0x173/0x300&lt;/p&gt;
&lt;p&gt;Allocated by task 86:
   hci_inquiry_cache_update+0x483/0x940
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 91:
   hci_inquiry_cache_flush+0x13e/0x2f0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x26…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98737</guid>
    </item>
    <item>
      <title>GHSA-g43c-xvh2-vxh2</title>
      <link>https://db.gcve.eu/vuln/ghsa-g43c-xvh2-vxh2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Fix inquiry cache use-after-free&lt;/p&gt;
&lt;p&gt;The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates
and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and
hci_stop_discovery_sync() look up entries and read their fields without
taking hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire
hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads
the freed entry while preparing a create-connection or remote-name-cancel
command. The list traversal also races with cache updates and removal.&lt;/p&gt;
&lt;p&gt;KASAN reported these accesses:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_acl_create_conn_sync+0x5f1/0x650
   hci_cmd_sync_work+0x13c/0x290&lt;/p&gt;
&lt;p&gt;Allocated by task 90:
   hci_inquiry_cache_update+0x3e6/0x7d0
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 93:
   hci_inquiry_cache_flush+0x111/0x2b0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x269/0x5f0&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_stop_discovery_sync+0x3b1/0x3c0
   hci_cmd_sync_work+0x173/0x300&lt;/p&gt;
&lt;p&gt;Allocated by task 86:
   hci_inquiry_cache_update+0x483/0x940
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 91:
   hci_inquiry_cache_flush+0x13e/0x2f0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x26…&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: Fix inquiry cache use-after-free&lt;/p&gt;
&lt;p&gt;The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates
and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and
hci_stop_discovery_sync() look up entries and read their fields without
taking hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire
hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads
the freed entry while preparing a create-connection or remote-name-cancel
command. The list traversal also races with cache updates and removal.&lt;/p&gt;
&lt;p&gt;KASAN reported these accesses:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_acl_create_conn_sync+0x5f1/0x650
   hci_cmd_sync_work+0x13c/0x290&lt;/p&gt;
&lt;p&gt;Allocated by task 90:
   hci_inquiry_cache_update+0x3e6/0x7d0
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 93:
   hci_inquiry_cache_flush+0x111/0x2b0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x269/0x5f0&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0
  Workqueue: hci0 hci_cmd_sync_work
  Call Trace:
   hci_stop_discovery_sync+0x3b1/0x3c0
   hci_cmd_sync_work+0x173/0x300&lt;/p&gt;
&lt;p&gt;Allocated by task 86:
   hci_inquiry_cache_update+0x483/0x940
   hci_inquiry_result_evt+0x3cb/0x560&lt;/p&gt;
&lt;p&gt;Freed by task 91:
   hci_inquiry_cache_flush+0x13e/0x2f0
   hci_inquiry+0x2f2/0x780
   hci_sock_ioctl+0x26…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g43c-xvh2-vxh2</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98737 — Bluetooth: hci_sync: Fix inquiry cache use-after-free</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98737</link>
      <description>msrc_CVE-2026-98737</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98737</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98737</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98737</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: Fix inquiry cache use-after-free The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and hci_stop_discovery_sync() look up entries and read their fields without taking hdev-&amp;gt;lock. After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal. KASAN reported these accesses:   BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650   Workqueue: hci0 hci_cmd_sync_work   Call Trace:    hci_acl_create_conn_sync+0x5f1/0x650    hci_cmd_sync_work+0x13c/0x290   Allocated by task 90:    hci_inquiry_cache_update+0x3e6/0x7d0    hci_inquiry_result_evt+0x3cb/0x560   Freed by task 93:    hci_inquiry_cache_flush+0x111/0x2b0    hci_inquiry+0x2f2/0x780    hci_sock_ioctl+0x269/0x5f0   BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0   Workqueue: hci0 hci_cmd_sync_work   Call Trace:    hci_stop_discovery_sync+0x3b1/0x3c0    hci_cmd_sync_work+0x173/0x300   Allocated by task 86:    hci_inquiry_cache_update+0x483/0x940    hci_inquiry_result_evt+0x3cb/0x560   Freed by task 91:    hci_inquiry_cache_flush+0x13e/0x2f0    hci_inquiry+0x2f2/0x780    hci_sock_ioctl+0x269/0x5f0 Ho…&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: Fix inquiry cache use-after-free The sync command worker holds hdev-&amp;gt;req_lock, but inquiry-cache updates and flushes use hdev-&amp;gt;lock. Both hci_acl_create_conn_sync() and hci_stop_discovery_sync() look up entries and read their fields without taking hdev-&amp;gt;lock. After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire hdev-&amp;gt;lock and flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal. KASAN reported these accesses:   BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650   Workqueue: hci0 hci_cmd_sync_work   Call Trace:    hci_acl_create_conn_sync+0x5f1/0x650    hci_cmd_sync_work+0x13c/0x290   Allocated by task 90:    hci_inquiry_cache_update+0x3e6/0x7d0    hci_inquiry_result_evt+0x3cb/0x560   Freed by task 93:    hci_inquiry_cache_flush+0x111/0x2b0    hci_inquiry+0x2f2/0x780    hci_sock_ioctl+0x269/0x5f0   BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0   Workqueue: hci0 hci_cmd_sync_work   Call Trace:    hci_stop_discovery_sync+0x3b1/0x3c0    hci_cmd_sync_work+0x173/0x300   Allocated by task 86:    hci_inquiry_cache_update+0x483/0x940    hci_inquiry_result_evt+0x3cb/0x560   Freed by task 91:    hci_inquiry_cache_flush+0x13e/0x2f0    hci_inquiry+0x2f2/0x780    hci_sock_ioctl+0x269/0x5f0 Ho…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98737</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
