<?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>Thu, 01 Oct 2026 15:45:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64407</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64407</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-64407</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1031 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031</link>
      <description>certfr-2026-avi-1031</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64407</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64407</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()&lt;/p&gt;
&lt;p&gt;During the v3 firmware download the controller sends a v3_data_req with a
32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower
bound of the offset and then sends firmware from that offset.&lt;/p&gt;
&lt;p&gt;nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;
  serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +
                          nxpdev-&amp;gt;fw_dnld_v3_offset, len);&lt;/p&gt;
&lt;p&gt;Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size,
so a controller that asks for an offset or length past the firmware image
makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that
memory back over UART.&lt;/p&gt;
&lt;p&gt;nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent
check to the v3 path, reject the request when it falls outside the firmware
image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at
free_skb stays consistent.&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: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()&lt;/p&gt;
&lt;p&gt;During the v3 firmware download the controller sends a v3_data_req with a
32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower
bound of the offset and then sends firmware from that offset.&lt;/p&gt;
&lt;p&gt;nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;
  serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +
                          nxpdev-&amp;gt;fw_dnld_v3_offset, len);&lt;/p&gt;
&lt;p&gt;Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size,
so a controller that asks for an offset or length past the firmware image
makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that
memory back over UART.&lt;/p&gt;
&lt;p&gt;nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent
check to the v3 path, reject the request when it falls outside the firmware
image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at
free_skb stays consistent.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64407</guid>
    </item>
    <item>
      <title>GHSA-vpwp-65cp-hgqm</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vpwp-65cp-hgqm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()&lt;/p&gt;
&lt;p&gt;During the v3 firmware download the controller sends a v3_data_req with a
32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower
bound of the offset and then sends firmware from that offset.&lt;/p&gt;
&lt;p&gt;nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;
  serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +
                          nxpdev-&amp;gt;fw_dnld_v3_offset, len);&lt;/p&gt;
&lt;p&gt;Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size,
so a controller that asks for an offset or length past the firmware image
makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that
memory back over UART.&lt;/p&gt;
&lt;p&gt;nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent
check to the v3 path, reject the request when it falls outside the firmware
image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at
free_skb stays consistent.&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: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()&lt;/p&gt;
&lt;p&gt;During the v3 firmware download the controller sends a v3_data_req with a
32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower
bound of the offset and then sends firmware from that offset.&lt;/p&gt;
&lt;p&gt;nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;
  serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +
                          nxpdev-&amp;gt;fw_dnld_v3_offset, len);&lt;/p&gt;
&lt;p&gt;Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size,
so a controller that asks for an offset or length past the firmware image
makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that
memory back over UART.&lt;/p&gt;
&lt;p&gt;nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent
check to the v3 path, reject the request when it falls outside the firmware
image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at
free_skb stays consistent.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vpwp-65cp-hgqm</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64407 — Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-64407</link>
      <description>msrc_CVE-2026-64407</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-64407</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23881-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64407</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64407</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() During the v3 firmware download the controller sends a v3_data_req with a 32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower bound of the offset and then sends firmware from that offset.   nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;   serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +                           nxpdev-&amp;gt;fw_dnld_v3_offset, len); Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size, so a controller that asks for an offset or length past the firmware image makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that memory back over UART. nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent check to the v3 path, reject the request when it falls outside the firmware image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at free_skb stays consistent.&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() During the v3 firmware download the controller sends a v3_data_req with a 32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower bound of the offset and then sends firmware from that offset.   nxpdev-&amp;gt;fw_dnld_v3_offset = offset - nxpdev-&amp;gt;fw_v3_offset_correction;   serdev_device_write_buf(nxpdev-&amp;gt;serdev, nxpdev-&amp;gt;fw-&amp;gt;data +                           nxpdev-&amp;gt;fw_dnld_v3_offset, len); Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&amp;gt;fw-&amp;gt;size, so a controller that asks for an offset or length past the firmware image makes the driver read past the end of nxpdev-&amp;gt;fw-&amp;gt;data and send that memory back over UART. nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent check to the v3 path, reject the request when it falls outside the firmware image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at free_skb stays consistent.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64407</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</guid>
    </item>
  </channel>
</rss>
