<?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>Tue, 17 Nov 2026 10:37:39 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99009</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99009</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-99009</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1473 — 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-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396124</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396124</link>
      <description>EUVD-2026-396124</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396124</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99009</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99009</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex&lt;/p&gt;
&lt;p&gt;An RFCOMM connect() issued while a BR/EDR link is being authenticated
makes lockdep report a circular dependency, and the reported cycle is a
real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&amp;gt;lock:&lt;/p&gt;
&lt;p&gt;hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]&lt;/p&gt;
&lt;p&gt;while an RFCOMM connect() from userspace takes the same two locks the
other way round:&lt;/p&gt;
&lt;p&gt;rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&amp;gt;lock]&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
  kworker/u131:1/1128 is trying to acquire lock:
  rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]
  but task is already holding lock:
  hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0
  Chain exists of:
    rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock&lt;/p&gt;
&lt;p&gt;hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.&lt;/p&gt;
&lt;p&gt;Both orders have to be seen in the same boot, which is why a BR/EDR
connection alone is not enough to show it: a session set up by the
r…&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: RFCOMM: connect the session socket without rfcomm_mutex&lt;/p&gt;
&lt;p&gt;An RFCOMM connect() issued while a BR/EDR link is being authenticated
makes lockdep report a circular dependency, and the reported cycle is a
real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&amp;gt;lock:&lt;/p&gt;
&lt;p&gt;hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]&lt;/p&gt;
&lt;p&gt;while an RFCOMM connect() from userspace takes the same two locks the
other way round:&lt;/p&gt;
&lt;p&gt;rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&amp;gt;lock]&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
  kworker/u131:1/1128 is trying to acquire lock:
  rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]
  but task is already holding lock:
  hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0
  Chain exists of:
    rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock&lt;/p&gt;
&lt;p&gt;hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.&lt;/p&gt;
&lt;p&gt;Both orders have to be seen in the same boot, which is why a BR/EDR
connection alone is not enough to show it: a session set up by the
r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99009</guid>
    </item>
    <item>
      <title>GHSA-5rpp-jh2w-vm6p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5rpp-jh2w-vm6p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex&lt;/p&gt;
&lt;p&gt;An RFCOMM connect() issued while a BR/EDR link is being authenticated
makes lockdep report a circular dependency, and the reported cycle is a
real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&amp;gt;lock:&lt;/p&gt;
&lt;p&gt;hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]&lt;/p&gt;
&lt;p&gt;while an RFCOMM connect() from userspace takes the same two locks the
other way round:&lt;/p&gt;
&lt;p&gt;rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&amp;gt;lock]&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
  kworker/u131:1/1128 is trying to acquire lock:
  rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]
  but task is already holding lock:
  hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0
  Chain exists of:
    rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock&lt;/p&gt;
&lt;p&gt;hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.&lt;/p&gt;
&lt;p&gt;Both orders have to be seen in the same boot, which is why a BR/EDR
connection alone is not enough to show it: a session set up by the
r…&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: RFCOMM: connect the session socket without rfcomm_mutex&lt;/p&gt;
&lt;p&gt;An RFCOMM connect() issued while a BR/EDR link is being authenticated
makes lockdep report a circular dependency, and the reported cycle is a
real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock.&lt;/p&gt;
&lt;p&gt;rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&amp;gt;lock:&lt;/p&gt;
&lt;p&gt;hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]&lt;/p&gt;
&lt;p&gt;while an RFCOMM connect() from userspace takes the same two locks the
other way round:&lt;/p&gt;
&lt;p&gt;rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&amp;gt;lock]&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
  kworker/u131:1/1128 is trying to acquire lock:
  rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]
  but task is already holding lock:
  hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0
  Chain exists of:
    rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock&lt;/p&gt;
&lt;p&gt;hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.&lt;/p&gt;
&lt;p&gt;Both orders have to be seen in the same boot, which is why a BR/EDR
connection alone is not enough to show it: a session set up by the
r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5rpp-jh2w-vm6p</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99009 — Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99009</link>
      <description>msrc_CVE-2026-99009</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99009</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99009</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99009</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 180 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex An RFCOMM connect() issued while a BR/EDR link is being authenticated makes lockdep report a circular dependency, and the reported cycle is a real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock. rfcomm_security_cfm() is called from the HCI event path, which already holds hdev-&amp;gt;lock:   hci_rx_work()     hci_event_packet()       hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]         hci_encrypt_cfm()          [hci_cb_list_lock]           rfcomm_security_cfm()    [rfcomm_mutex] while an RFCOMM connect() from userspace takes the same two locks the other way round:   rfcomm_sock_connect()     rfcomm_dlc_open()              [rfcomm_mutex]       __rfcomm_dlc_open()         rfcomm_session_create()           kernel_connect()             l2cap_sock_connect()               l2cap_chan_connect() [hdev-&amp;gt;lock]   WARNING: possible circular locking dependency detected   kworker/u131:1/1128 is trying to acquire lock:   rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]   but task is already holding lock:   hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0   Chain exists of:     rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback the same way. Both orders have to be seen in the same boot, which is why a BR/EDR connection alone is not enough to show it: a session set up by the remote sid…&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 180 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex An RFCOMM connect() issued while a BR/EDR link is being authenticated makes lockdep report a circular dependency, and the reported cycle is a real AB/BA between rfcomm_mutex and hdev-&amp;gt;lock. rfcomm_security_cfm() is called from the HCI event path, which already holds hdev-&amp;gt;lock:   hci_rx_work()     hci_event_packet()       hci_cc_read_enc_key_size()   [hdev-&amp;gt;lock]         hci_encrypt_cfm()          [hci_cb_list_lock]           rfcomm_security_cfm()    [rfcomm_mutex] while an RFCOMM connect() from userspace takes the same two locks the other way round:   rfcomm_sock_connect()     rfcomm_dlc_open()              [rfcomm_mutex]       __rfcomm_dlc_open()         rfcomm_session_create()           kernel_connect()             l2cap_sock_connect()               l2cap_chan_connect() [hdev-&amp;gt;lock]   WARNING: possible circular locking dependency detected   kworker/u131:1/1128 is trying to acquire lock:   rfcomm_mutex, at: rfcomm_security_cfm+0x31/0x3e0 [rfcomm]   but task is already holding lock:   hci_cb_list_lock, at: hci_cc_read_enc_key_size+0x1d2/0xcc0   Chain exists of:     rfcomm_mutex --&amp;gt; &amp;amp;hdev-&amp;gt;lock --&amp;gt; hci_cb_list_lock hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback the same way. Both orders have to be seen in the same boot, which is why a BR/EDR connection alone is not enough to show it: a session set up by the remote sid…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99009</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</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://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
