<?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://cve.radiocsirt.org</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 20:55:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64573</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64573</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64573</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1030 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1030</link>
      <description>certfr-2026-avi-1030</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1030</guid>
    </item>
    <item>
      <title>EUVD-2026-355986</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-355986</link>
      <description>EUVD-2026-355986</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-355986</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64573</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64573</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: qca: fix NVM tag length underflow in TLV parser&lt;/p&gt;
&lt;p&gt;In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is
&amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed
int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a
size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied
&amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body
then reads a 12-byte struct tlv_type_nvm past the end of the short
vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it).&lt;/p&gt;
&lt;p&gt;Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both
operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too
small for one record correctly skips the loop.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)
  Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52
  Workqueue: hci0 hci_power_on
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)
   qca_uart_setup (drivers/bluetooth/btqca.c:948)
   qca_setup (drivers/bluetooth/hci_qca.c:2029)
   hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)
   hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)
   hci_power_on (net/bluetooth/hci_core.c:920)
   process_one_work (kernel/workqueue.c:3322)
   worker_thread…&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: qca: fix NVM tag length underflow in TLV parser&lt;/p&gt;
&lt;p&gt;In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is
&amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed
int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a
size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied
&amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body
then reads a 12-byte struct tlv_type_nvm past the end of the short
vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it).&lt;/p&gt;
&lt;p&gt;Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both
operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too
small for one record correctly skips the loop.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)
  Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52
  Workqueue: hci0 hci_power_on
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)
   qca_uart_setup (drivers/bluetooth/btqca.c:948)
   qca_setup (drivers/bluetooth/hci_qca.c:2029)
   hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)
   hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)
   hci_power_on (net/bluetooth/hci_core.c:920)
   process_one_work (kernel/workqueue.c:3322)
   worker_thread…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64573</guid>
    </item>
    <item>
      <title>GHSA-xx6f-xq9m-7gmm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xx6f-xq9m-7gmm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: qca: fix NVM tag length underflow in TLV parser&lt;/p&gt;
&lt;p&gt;In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is
&amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed
int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a
size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied
&amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body
then reads a 12-byte struct tlv_type_nvm past the end of the short
vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it).&lt;/p&gt;
&lt;p&gt;Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both
operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too
small for one record correctly skips the loop.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)
  Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52
  Workqueue: hci0 hci_power_on
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)
   qca_uart_setup (drivers/bluetooth/btqca.c:948)
   qca_setup (drivers/bluetooth/hci_qca.c:2029)
   hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)
   hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)
   hci_power_on (net/bluetooth/hci_core.c:920)
   process_one_work (kernel/workqueue.c:3322)
   worker_thread…&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: qca: fix NVM tag length underflow in TLV parser&lt;/p&gt;
&lt;p&gt;In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is
&amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed
int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a
size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied
&amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body
then reads a 12-byte struct tlv_type_nvm past the end of the short
vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it).&lt;/p&gt;
&lt;p&gt;Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both
operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too
small for one record correctly skips the loop.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)
  Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52
  Workqueue: hci0 hci_power_on
  Call Trace:
   ...
   kasan_report (mm/kasan/report.c:595)
   qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)
   qca_uart_setup (drivers/bluetooth/btqca.c:948)
   qca_setup (drivers/bluetooth/hci_qca.c:2029)
   hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)
   hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)
   hci_power_on (net/bluetooth/hci_core.c:920)
   process_one_work (kernel/workqueue.c:3322)
   worker_thread…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xx6f-xq9m-7gmm</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64573 — Bluetooth: qca: fix NVM tag length underflow in TLV parser</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-64573</link>
      <description>msrc_CVE-2026-64573</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-64573</guid>
    </item>
    <item>
      <title>OESA-2026-3532 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3532</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3532</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-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://cve.radiocsirt.org/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64573</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64573</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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is &amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied &amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too small for one record correctly skips the loop.   BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)   Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52   Workqueue: hci0 hci_power_on   Call Trace:    ...    kasan_report (mm/kasan/report.c:595)    qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)    qca_uart_setup (drivers/bluetooth/btqca.c:948)    qca_setup (drivers/bluetooth/hci_qca.c:2029)    hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)    hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)    hci_power_on (net/bluetooth/hci_core.c:920)    process_one_work (kernel/workqueue.c:3322)    worker_thread (ker…&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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is &amp;#34;while (idx &amp;lt; length - sizeof(struct tlv_type_nvm))&amp;#34;. &amp;#34;length&amp;#34; is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so &amp;#34;length&amp;#34; is converted to size_t and any firmware-supplied &amp;#34;length&amp;#34; &amp;lt; 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc&amp;#39;d firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as &amp;#34;idx + sizeof(struct tlv_type_nvm) &amp;lt;= length&amp;#34;; both operands are non-negative, so it no longer underflows and a &amp;#34;length&amp;#34; too small for one record correctly skips the loop.   BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)   Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52   Workqueue: hci0 hci_power_on   Call Trace:    ...    kasan_report (mm/kasan/report.c:595)    qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)    qca_uart_setup (drivers/bluetooth/btqca.c:948)    qca_setup (drivers/bluetooth/hci_qca.c:2029)    hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438)    hci_dev_open_sync (net/bluetooth/hci_sync.c:5227)    hci_power_on (net/bluetooth/hci_core.c:920)    process_one_work (kernel/workqueue.c:3322)    worker_thread (ker…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64573</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2659 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2659</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um den Speicher zu beschädigen, einen Denial-of-Service-Zustand auszulösen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um den Speicher zu beschädigen, einen Denial-of-Service-Zustand auszulösen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2659</guid>
    </item>
  </channel>
</rss>
