<?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:50:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38250 — Bluetooth: hci_core: Fix use-after-free in vhci_flush()</title>
      <link>https://db.gcve.eu/vuln/cve-2025-38250</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_core: Fix use-after-free in vhci_flush()&lt;/p&gt;
&lt;p&gt;syzbot reported use-after-free in vhci_flush() without repro. [0]&lt;/p&gt;
&lt;p&gt;From the splat, a thread close()d a vhci file descriptor while
its device was being used by iotcl() on another thread.&lt;/p&gt;
&lt;p&gt;Once the last fd refcnt is released, vhci_release() calls
hci_unregister_dev(), hci_free_dev(), and kfree() for struct
vhci_data, which is set to hci_dev-&amp;gt;dev-&amp;gt;driver_data.&lt;/p&gt;
&lt;p&gt;The problem is that there is no synchronisation after unlinking
hdev from hci_dev_list in hci_unregister_dev().  There might be
another thread still accessing the hdev which was fetched before
the unlink operation.&lt;/p&gt;
&lt;p&gt;We can use SRCU for such synchronisation.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s run hci_dev_reset() under SRCU and wait for its completion
in hci_unregister_dev().&lt;/p&gt;
&lt;p&gt;Another option would be to restore hci_dev-&amp;gt;destruct(), which was
removed in commit 587ae086f6e4 (&amp;#34;Bluetooth: Remove unused
hci-destruct cb&amp;#34;).  However, this would not be a good solution, as
we should not run hci_unregister_dev() while there are in-flight
ioctl() requests, which could lead to another data-race KCSAN splat.&lt;/p&gt;
&lt;p&gt;Note that other drivers seem to have the same problem, for exmaple,
virtbt_remove().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: KASAN: slab-use-after-free in skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]
BUG: KASAN: slab-use-after-free in skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937
Read of size 8 at addr ffff88807cb8d858 by task syz.1.21…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_core: Fix use-after-free in vhci_flush()&lt;/p&gt;
&lt;p&gt;syzbot reported use-after-free in vhci_flush() without repro. [0]&lt;/p&gt;
&lt;p&gt;From the splat, a thread close()d a vhci file descriptor while
its device was being used by iotcl() on another thread.&lt;/p&gt;
&lt;p&gt;Once the last fd refcnt is released, vhci_release() calls
hci_unregister_dev(), hci_free_dev(), and kfree() for struct
vhci_data, which is set to hci_dev-&amp;gt;dev-&amp;gt;driver_data.&lt;/p&gt;
&lt;p&gt;The problem is that there is no synchronisation after unlinking
hdev from hci_dev_list in hci_unregister_dev().  There might be
another thread still accessing the hdev which was fetched before
the unlink operation.&lt;/p&gt;
&lt;p&gt;We can use SRCU for such synchronisation.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s run hci_dev_reset() under SRCU and wait for its completion
in hci_unregister_dev().&lt;/p&gt;
&lt;p&gt;Another option would be to restore hci_dev-&amp;gt;destruct(), which was
removed in commit 587ae086f6e4 (&amp;#34;Bluetooth: Remove unused
hci-destruct cb&amp;#34;).  However, this would not be a good solution, as
we should not run hci_unregister_dev() while there are in-flight
ioctl() requests, which could lead to another data-race KCSAN splat.&lt;/p&gt;
&lt;p&gt;Note that other drivers seem to have the same problem, for exmaple,
virtbt_remove().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: KASAN: slab-use-after-free in skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]
BUG: KASAN: slab-use-after-free in skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937
Read of size 8 at addr ffff88807cb8d858 by task syz.1.21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-38250</guid>
    </item>
    <item>
      <title>USN-7833-1 — linux, linux-aws, linux-gcp, linux-oem-6.14, linux-oracle, linux-oracle-6.14, linux-raspi, linux-realtime vulnerabiliti…</title>
      <link>https://db.gcve.eu/vuln/usn-7833-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-oem-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,
and Flavien Solt discovered that some AMD processors may allow an attacker
to infer data from previous stores, potentially resulting in the leakage of
privileged information. A local attacker could possibly use this to expose
sensitive information. (CVE-2024-36350, CVE-2024-36357)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Ublk userspace block driver;
  - Bus devices;
  - DMA engine subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - Cirrus firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - TI TPS6594 PFSM driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - x86 platform drivers;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - ChipIdea USB dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-oem-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Oleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,
and Flavien Solt discovered that some AMD processors may allow an attacker
to infer data from previous stores, potentially resulting in the leakage of
privileged information. A local attacker could possibly use this to expose
sensitive information. (CVE-2024-36350, CVE-2024-36357)&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:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Ublk userspace block driver;
  - Bus devices;
  - DMA engine subsystem;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - Cirrus firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - TI TPS6594 PFSM driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - NVME drivers;
  - x86 platform drivers;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - TCM subsystem;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - ChipIdea USB dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7833-1</guid>
    </item>
  </channel>
</rss>
