<?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 14:10:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11590</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11590</link>
      <description>bdu:2026-11590</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11590</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23146</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23146</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-23146</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</link>
      <description>certfr-2026-avi-0316</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</guid>
    </item>
    <item>
      <title>EUVD-2026-326731</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326731</link>
      <description>EUVD-2026-326731</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326731</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23146</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23146</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work&lt;/p&gt;
&lt;p&gt;hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling
hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize
hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window,
hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is
initialized, leading to a NULL pointer dereference in
hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv.&lt;/p&gt;
&lt;p&gt;The race condition is:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  ----                              ----
  hci_uart_set_proto()
    set_bit(HCI_UART_PROTO_INIT)
    hci_uart_register_dev()
                                    tty write wakeup
                                      hci_uart_tty_wakeup()
                                        hci_uart_tx_wakeup()
                                          schedule_work(&amp;amp;hu-&amp;gt;write_work)
      proto-&amp;gt;open(hu)
        // initializes hu-&amp;gt;priv
                                    hci_uart_write_work()
                                      hci_uart_dequeue()
                                        proto-&amp;gt;dequeue(hu)
                                          // accesses hu-&amp;gt;priv (NULL!)&lt;/p&gt;
&lt;p&gt;Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open()
succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be
scheduled.&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_uart: fix null-ptr-deref in hci_uart_write_work&lt;/p&gt;
&lt;p&gt;hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling
hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize
hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window,
hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is
initialized, leading to a NULL pointer dereference in
hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv.&lt;/p&gt;
&lt;p&gt;The race condition is:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  ----                              ----
  hci_uart_set_proto()
    set_bit(HCI_UART_PROTO_INIT)
    hci_uart_register_dev()
                                    tty write wakeup
                                      hci_uart_tty_wakeup()
                                        hci_uart_tx_wakeup()
                                          schedule_work(&amp;amp;hu-&amp;gt;write_work)
      proto-&amp;gt;open(hu)
        // initializes hu-&amp;gt;priv
                                    hci_uart_write_work()
                                      hci_uart_dequeue()
                                        proto-&amp;gt;dequeue(hu)
                                          // accesses hu-&amp;gt;priv (NULL!)&lt;/p&gt;
&lt;p&gt;Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open()
succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be
scheduled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23146</guid>
    </item>
    <item>
      <title>GHSA-hcr8-x92w-q652</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hcr8-x92w-q652</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work&lt;/p&gt;
&lt;p&gt;hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling
hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize
hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window,
hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is
initialized, leading to a NULL pointer dereference in
hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv.&lt;/p&gt;
&lt;p&gt;The race condition is:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  ----                              ----
  hci_uart_set_proto()
    set_bit(HCI_UART_PROTO_INIT)
    hci_uart_register_dev()
                                    tty write wakeup
                                      hci_uart_tty_wakeup()
                                        hci_uart_tx_wakeup()
                                          schedule_work(&amp;amp;hu-&amp;gt;write_work)
      proto-&amp;gt;open(hu)
        // initializes hu-&amp;gt;priv
                                    hci_uart_write_work()
                                      hci_uart_dequeue()
                                        proto-&amp;gt;dequeue(hu)
                                          // accesses hu-&amp;gt;priv (NULL!)&lt;/p&gt;
&lt;p&gt;Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open()
succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be
scheduled.&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_uart: fix null-ptr-deref in hci_uart_write_work&lt;/p&gt;
&lt;p&gt;hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling
hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize
hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window,
hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is
initialized, leading to a NULL pointer dereference in
hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv.&lt;/p&gt;
&lt;p&gt;The race condition is:&lt;/p&gt;
&lt;p&gt;CPU0                              CPU1
  ----                              ----
  hci_uart_set_proto()
    set_bit(HCI_UART_PROTO_INIT)
    hci_uart_register_dev()
                                    tty write wakeup
                                      hci_uart_tty_wakeup()
                                        hci_uart_tx_wakeup()
                                          schedule_work(&amp;amp;hu-&amp;gt;write_work)
      proto-&amp;gt;open(hu)
        // initializes hu-&amp;gt;priv
                                    hci_uart_write_work()
                                      hci_uart_dequeue()
                                        proto-&amp;gt;dequeue(hu)
                                          // accesses hu-&amp;gt;priv (NULL!)&lt;/p&gt;
&lt;p&gt;Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open()
succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be
scheduled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hcr8-x92w-q652</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20416-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-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/opensuse-su-2026:20416-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0962-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0962-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:0962-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23146</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23146</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 173 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window, hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is initialized, leading to a NULL pointer dereference in hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv. The race condition is:   CPU0                              CPU1   ----                              ----   hci_uart_set_proto()     set_bit(HCI_UART_PROTO_INIT)     hci_uart_register_dev()                                     tty write wakeup                                       hci_uart_tty_wakeup()                                         hci_uart_tx_wakeup()                                           schedule_work(&amp;amp;hu-&amp;gt;write_work)       proto-&amp;gt;open(hu)         // initializes hu-&amp;gt;priv                                     hci_uart_write_work()                                       hci_uart_dequeue()                                         proto-&amp;gt;dequeue(hu)                                           // accesses hu-&amp;gt;priv (NULL!) Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open() succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be scheduled.&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 173 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling hci_uart_register_dev(), which calls proto-&amp;gt;open() to initialize hu-&amp;gt;priv. However, if a TTY write wakeup occurs during this window, hci_uart_tx_wakeup() may schedule write_work before hu-&amp;gt;priv is initialized, leading to a NULL pointer dereference in hci_uart_write_work() when proto-&amp;gt;dequeue() accesses hu-&amp;gt;priv. The race condition is:   CPU0                              CPU1   ----                              ----   hci_uart_set_proto()     set_bit(HCI_UART_PROTO_INIT)     hci_uart_register_dev()                                     tty write wakeup                                       hci_uart_tty_wakeup()                                         hci_uart_tx_wakeup()                                           schedule_work(&amp;amp;hu-&amp;gt;write_work)       proto-&amp;gt;open(hu)         // initializes hu-&amp;gt;priv                                     hci_uart_write_work()                                       hci_uart_dequeue()                                         proto-&amp;gt;dequeue(hu)                                           // accesses hu-&amp;gt;priv (NULL!) Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto-&amp;gt;open() succeeds, ensuring hu-&amp;gt;priv is initialized before any work can be scheduled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23146</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0421 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&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, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421</guid>
    </item>
  </channel>
</rss>
