<?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>Thu, 19 Nov 2026 17:23:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93247 — Bluetooth: mgmt: fix 'hdev-&gt;discovery.uuids' NULL dereference</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93247</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: mgmt: fix &amp;#39;hdev-&amp;gt;discovery.uuids&amp;#39; NULL dereference&lt;/p&gt;
&lt;p&gt;&amp;#39;uuid_count&amp;#39; member of struct &amp;#39;discovery_state&amp;#39; is assigned and read
without any locks, so there is a chance of situation when
uuid_count != 0, but uuids is NULL and there will be NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Possible race:
&amp;#39;hci_update_passive_scan_sync&amp;#39;
  &amp;#39;hci_discovery_filter_clear&amp;#39;
    hdev-&amp;gt;discovery.uuid_count = 0;
      &amp;lt;----------------------preempted-----------------------------&amp;gt;
                        &amp;#39;start_service_discovery&amp;#39;
                          // Set uuid_count to value != 0
                          hdev-&amp;gt;discovery.uuid_count = uuid_count;
                          hdev-&amp;gt;discovery.uuids = kmemdup(...);
      &amp;lt;----------------------preempted-----------------------------&amp;gt;
    spin_lock(&amp;amp;hdev-&amp;gt;discovery.lock);
    kfree(hdev-&amp;gt;discovery.uuids);
    hdev-&amp;gt;discovery.uuids = NULL;
    spin_unlock(&amp;amp;hdev-&amp;gt;discovery.lock);&lt;/p&gt;
&lt;p&gt;Now uuids == NULL and uuid_count != 0.
So &amp;#39;mgmt_device_found&amp;#39; -&amp;gt; &amp;#39;is_filter_match&amp;#39; -&amp;gt; &amp;#39;eir_has_uuids&amp;#39; receives
non consistent discovery state, where NULL dereference of uuids happens.&lt;/p&gt;
&lt;p&gt;To fix it let&amp;#39;s add discovery.lock around every read/write of uuid_count,
uuids pair of struct members. It is also important to assign uuid_count
value only after success kmemdup() allocation in
start_service_discovery(), otherwise uuids is NULL, because kmemdup failed,
but uuid_count is already assigned to non zero value.&lt;/p&gt;
&lt;p&gt;The followin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: mgmt: fix &amp;#39;hdev-&amp;gt;discovery.uuids&amp;#39; NULL dereference&lt;/p&gt;
&lt;p&gt;&amp;#39;uuid_count&amp;#39; member of struct &amp;#39;discovery_state&amp;#39; is assigned and read
without any locks, so there is a chance of situation when
uuid_count != 0, but uuids is NULL and there will be NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Possible race:
&amp;#39;hci_update_passive_scan_sync&amp;#39;
  &amp;#39;hci_discovery_filter_clear&amp;#39;
    hdev-&amp;gt;discovery.uuid_count = 0;
      &amp;lt;----------------------preempted-----------------------------&amp;gt;
                        &amp;#39;start_service_discovery&amp;#39;
                          // Set uuid_count to value != 0
                          hdev-&amp;gt;discovery.uuid_count = uuid_count;
                          hdev-&amp;gt;discovery.uuids = kmemdup(...);
      &amp;lt;----------------------preempted-----------------------------&amp;gt;
    spin_lock(&amp;amp;hdev-&amp;gt;discovery.lock);
    kfree(hdev-&amp;gt;discovery.uuids);
    hdev-&amp;gt;discovery.uuids = NULL;
    spin_unlock(&amp;amp;hdev-&amp;gt;discovery.lock);&lt;/p&gt;
&lt;p&gt;Now uuids == NULL and uuid_count != 0.
So &amp;#39;mgmt_device_found&amp;#39; -&amp;gt; &amp;#39;is_filter_match&amp;#39; -&amp;gt; &amp;#39;eir_has_uuids&amp;#39; receives
non consistent discovery state, where NULL dereference of uuids happens.&lt;/p&gt;
&lt;p&gt;To fix it let&amp;#39;s add discovery.lock around every read/write of uuid_count,
uuids pair of struct members. It is also important to assign uuid_count
value only after success kmemdup() allocation in
start_service_discovery(), otherwise uuids is NULL, because kmemdup failed,
but uuid_count is already assigned to non zero value.&lt;/p&gt;
&lt;p&gt;The followin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93247</guid>
    </item>
    <item>
      <title>USN-8959-1 — linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8959-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8959-1</guid>
    </item>
  </channel>
</rss>
