<?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, 02 Oct 2026 16:34:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38592 — Bluetooth: hci_devcd_dump: fix out-of-bounds via dev_coredumpv</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38592</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: hci_devcd_dump: fix out-of-bounds via dev_coredumpv&lt;/p&gt;
&lt;p&gt;Currently both dev_coredumpv and skb_put_data in hci_devcd_dump use
hdev-&amp;gt;dump.head. However, dev_coredumpv can free the buffer. From
dev_coredumpm_timeout documentation, which is used by dev_coredumpv:&lt;/p&gt;
&lt;p&gt;&amp;gt; Creates a new device coredump for the given device. If a previous one hasn&amp;#39;t
    &amp;gt; been read yet, the new coredump is discarded. The data lifetime is determined
    &amp;gt; by the device coredump framework and when it is no longer needed the @free
    &amp;gt; function will be called to free the data.&lt;/p&gt;
&lt;p&gt;If the data has not been read by the userspace yet, dev_coredumpv will
discard new buffer, freeing hdev-&amp;gt;dump.head. This leads to
vmalloc-out-of-bounds error when skb_put_data tries to access
hdev-&amp;gt;dump.head.&lt;/p&gt;
&lt;p&gt;A crash report from syzbot illustrates this:&lt;/p&gt;
&lt;p&gt;==================================================================
    BUG: KASAN: vmalloc-out-of-bounds in skb_put_data
    include/linux/skbuff.h:2752 [inline]
    BUG: KASAN: vmalloc-out-of-bounds in hci_devcd_dump+0x142/0x240
    net/bluetooth/coredump.c:258
    Read of size 140 at addr ffffc90004ed5000 by task kworker/u9:2/5844&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 5844 Comm: kworker/u9:2 Not tainted
    6.14.0-syzkaller-10892-g4e82c87058f4 #0 PREEMPT(full)
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
    Google 02/12/2025
    Workqueue: hci0 hci_devcd_timeout
    Call Trace:…&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: hci_devcd_dump: fix out-of-bounds via dev_coredumpv&lt;/p&gt;
&lt;p&gt;Currently both dev_coredumpv and skb_put_data in hci_devcd_dump use
hdev-&amp;gt;dump.head. However, dev_coredumpv can free the buffer. From
dev_coredumpm_timeout documentation, which is used by dev_coredumpv:&lt;/p&gt;
&lt;p&gt;&amp;gt; Creates a new device coredump for the given device. If a previous one hasn&amp;#39;t
    &amp;gt; been read yet, the new coredump is discarded. The data lifetime is determined
    &amp;gt; by the device coredump framework and when it is no longer needed the @free
    &amp;gt; function will be called to free the data.&lt;/p&gt;
&lt;p&gt;If the data has not been read by the userspace yet, dev_coredumpv will
discard new buffer, freeing hdev-&amp;gt;dump.head. This leads to
vmalloc-out-of-bounds error when skb_put_data tries to access
hdev-&amp;gt;dump.head.&lt;/p&gt;
&lt;p&gt;A crash report from syzbot illustrates this:&lt;/p&gt;
&lt;p&gt;==================================================================
    BUG: KASAN: vmalloc-out-of-bounds in skb_put_data
    include/linux/skbuff.h:2752 [inline]
    BUG: KASAN: vmalloc-out-of-bounds in hci_devcd_dump+0x142/0x240
    net/bluetooth/coredump.c:258
    Read of size 140 at addr ffffc90004ed5000 by task kworker/u9:2/5844&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 5844 Comm: kworker/u9:2 Not tainted
    6.14.0-syzkaller-10892-g4e82c87058f4 #0 PREEMPT(full)
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
    Google 02/12/2025
    Workqueue: hci0 hci_devcd_timeout
    Call Trace:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38592</guid>
    </item>
  </channel>
</rss>
