<?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>Sat, 03 Oct 2026 22:25:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01317</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-01317</link>
      <description>bdu:2026-01317</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-01317</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-54210</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54210</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-54210</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-345416</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345416</link>
      <description>EUVD-2026-345416</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345416</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54210</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54210</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&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: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-54210</guid>
    </item>
    <item>
      <title>GHSA-58q4-73m8-4p8p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-58q4-73m8-4p8p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&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: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()&lt;/p&gt;
&lt;p&gt;KASAN reports that there&amp;#39;s a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under the
HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because
msft_remove_monitor() can end up freeing the monitor
structure. Specifically:
  hci_remove_adv_monitor() -&amp;gt;
  msft_remove_monitor() -&amp;gt;
  msft_remove_monitor_sync() -&amp;gt;
  msft_le_cancel_monitor_advertisement_cb() -&amp;gt;
  hci_free_adv_monitor()&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s
still valid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-58q4-73m8-4p8p</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54210</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54210</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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() KASAN reports that there&amp;#39;s a use-after-free in hci_remove_adv_monitor(). Trawling through the disassembly, you can see that the complaint is from the access in bt_dev_dbg() under the HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because msft_remove_monitor() can end up freeing the monitor structure. Specifically:   hci_remove_adv_monitor() -&amp;gt;   msft_remove_monitor() -&amp;gt;   msft_remove_monitor_sync() -&amp;gt;   msft_le_cancel_monitor_advertisement_cb() -&amp;gt;   hci_free_adv_monitor() Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s still valid.&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 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() KASAN reports that there&amp;#39;s a use-after-free in hci_remove_adv_monitor(). Trawling through the disassembly, you can see that the complaint is from the access in bt_dev_dbg() under the HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because msft_remove_monitor() can end up freeing the monitor structure. Specifically:   hci_remove_adv_monitor() -&amp;gt;   msft_remove_monitor() -&amp;gt;   msft_remove_monitor_sync() -&amp;gt;   msft_le_cancel_monitor_advertisement_cb() -&amp;gt;   hci_free_adv_monitor() Let&amp;#39;s fix the problem by just stashing the relevant data when it&amp;#39;s still valid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54210</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2941 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</link>
      <description>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</guid>
    </item>
  </channel>
</rss>
