<?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 04:32:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98601 — Bluetooth: btintel_pcie: validate device-supplied DMA indices</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98601</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: btintel_pcie: validate device-supplied DMA indices&lt;/p&gt;
&lt;p&gt;In btintel_pcie_msix_rx_handle(), the driver processes RX completion
descriptors (urbd1) written by the PCIe device into DMA-coherent memory.
urbd1-&amp;gt;frbd_tag (a 16-bit field fully controlled by the device firmware
via DMA) is used directly as an array index into rxq-&amp;gt;bufs[] without any
bounds check. rxq-&amp;gt;bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)
entries, while frbd_tag can be any value 0-65535. A malicious or
malfunctioning device can write an out-of-range frbd_tag, causing the
driver to dereference an out-of-bounds data_buf pointer.&lt;/p&gt;
&lt;p&gt;Additionally, cr_hia is read from a DMA-shared index array also writable
by the device; if the device sets cr_hia &amp;gt;= rxq-&amp;gt;count, the while-loop
never terminates because cr_tia is wrapped via modulo rxq-&amp;gt;count and can
never equal an out-of-range cr_hia.&lt;/p&gt;
&lt;p&gt;Add bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia
in the TX path. Log invalid values with bt_dev_err before returning.&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: btintel_pcie: validate device-supplied DMA indices&lt;/p&gt;
&lt;p&gt;In btintel_pcie_msix_rx_handle(), the driver processes RX completion
descriptors (urbd1) written by the PCIe device into DMA-coherent memory.
urbd1-&amp;gt;frbd_tag (a 16-bit field fully controlled by the device firmware
via DMA) is used directly as an array index into rxq-&amp;gt;bufs[] without any
bounds check. rxq-&amp;gt;bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)
entries, while frbd_tag can be any value 0-65535. A malicious or
malfunctioning device can write an out-of-range frbd_tag, causing the
driver to dereference an out-of-bounds data_buf pointer.&lt;/p&gt;
&lt;p&gt;Additionally, cr_hia is read from a DMA-shared index array also writable
by the device; if the device sets cr_hia &amp;gt;= rxq-&amp;gt;count, the while-loop
never terminates because cr_tia is wrapped via modulo rxq-&amp;gt;count and can
never equal an out-of-range cr_hia.&lt;/p&gt;
&lt;p&gt;Add bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia
in the TX path. Log invalid values with bt_dev_err before returning.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98601</guid>
    </item>
  </channel>
</rss>
