<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:09:21.858771+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-99009</id>
    <title>BELL-CVE-2026-99009</title>
    <updated>2026-11-17T10:09:21.871703+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99009"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</id>
    <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>
    <updated>2026-11-17T10:09:21.871758+00:00</updated>
    <content>certfr-2026-avi-1473</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396124</id>
    <title>EUVD-2026-396124</title>
    <updated>2026-11-17T10:09:21.871777+00:00</updated>
    <content>EUVD-2026-396124</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396124"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99009</id>
    <title>fkie_cve-2026-99009</title>
    <updated>2026-11-17T10:09:21.871788+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex</p>
<p>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-&gt;lock.</p>
<p>rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&gt;lock:</p>
<p>hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]</p>
<p>while an RFCOMM connect() from userspace takes the same two locks the
other way round:</p>
<p>rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&gt;lock]</p>
<p>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 --&gt; &amp;hdev-&gt;lock --&gt; hci_cb_list_lock</p>
<p>hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99009"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5rpp-jh2w-vm6p</id>
    <title>GHSA-5rpp-jh2w-vm6p</title>
    <updated>2026-11-17T10:09:21.871842+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex</p>
<p>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-&gt;lock.</p>
<p>rfcomm_security_cfm() is called from the HCI event path, which already
holds hdev-&gt;lock:</p>
<p>hci_rx_work()
    hci_event_packet()
      hci_cc_read_enc_key_size()   [hdev-&gt;lock]
        hci_encrypt_cfm()          [hci_cb_list_lock]
          rfcomm_security_cfm()    [rfcomm_mutex]</p>
<p>while an RFCOMM connect() from userspace takes the same two locks the
other way round:</p>
<p>rfcomm_sock_connect()
    rfcomm_dlc_open()              [rfcomm_mutex]
      __rfcomm_dlc_open()
        rfcomm_session_create()
          kernel_connect()
            l2cap_sock_connect()
              l2cap_chan_connect() [hdev-&gt;lock]</p>
<p>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 --&gt; &amp;hdev-&gt;lock --&gt; hci_cb_list_lock</p>
<p>hci_auth_complete_evt() and hci_encrypt_change_evt() reach the callback
the same way.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5rpp-jh2w-vm6p"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99009</id>
    <title>msrc_CVE-2026-99009 — Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex</title>
    <updated>2026-11-17T10:09:21.871883+00:00</updated>
    <content>msrc_CVE-2026-99009</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99009"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99009</id>
    <title>UBUNTU-CVE-2026-99009</title>
    <updated>2026-11-17T10:09:21.871899+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&gt;lock. rfcomm_security_cfm() is called from the HCI event path, which already holds hdev-&gt;lock:   hci_rx_work()     hci_event_packet()       hci_cc_read_enc_key_size()   [hdev-&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-&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 --&gt; &amp;hdev-&gt;lock --&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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99009"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</id>
    <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T10:09:21.872092+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152"/>
  </entry>
</feed>
