<?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>Mon, 02 Nov 2026 22:28:58 +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-98601</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98601</link>
      <description>&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;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/fkie_cve-2026-98601</guid>
    </item>
    <item>
      <title>GHSA-f3q9-4q8h-j7xp</title>
      <link>https://db.gcve.eu/vuln/ghsa-f3q9-4q8h-j7xp</link>
      <description>&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;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/ghsa-f3q9-4q8h-j7xp</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98601 — Bluetooth: btintel_pcie: validate device-supplied DMA indices</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98601</link>
      <description>msrc_CVE-2026-98601</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98601</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98601</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98601</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: validate device-supplied DMA indices 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. 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. 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; 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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: validate device-supplied DMA indices 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. 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. 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/ubuntu-cve-2026-98601</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>
