<?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:33:35.721126+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-99011</id>
    <title>BELL-CVE-2026-99011</title>
    <updated>2026-11-17T10:33:35.732524+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99011"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1535</id>
    <title>certfr-2026-avi-1535 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-17T10:33:35.732622+00:00</updated>
    <content>certfr-2026-avi-1535</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1535"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-392029</id>
    <title>EUVD-2026-392029</title>
    <updated>2026-11-17T10:33:35.732653+00:00</updated>
    <content>EUVD-2026-392029</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-392029"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99011</id>
    <title>fkie_cve-2026-99011</title>
    <updated>2026-11-17T10:33:35.732672+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: SCO: serialise sco_conn lifetime against sco_recv_scodata()</p>
<p>sco_recv_scodata() upgrades the weak hcon-&gt;sco_data back-pointer to a
strong reference under hdev-&gt;lock:</p>
<p>hci_dev_lock(hdev);
    hcon = hci_conn_hash_lookup_handle(hdev, handle);
    ...
    conn = sco_conn_hold_unless_zero(hcon-&gt;sco_data);
    hci_dev_unlock(hdev);</p>
<p>but the pointer is cleared from the other side without that lock. When
the last sco_conn reference is dropped, sco_conn_free() ran</p>
<p>conn-&gt;hcon-&gt;sco_data = NULL;</p>
<p>with no hdev-&gt;lock held, so the RX path could read hcon-&gt;sco_data and
call kref_get_unless_zero() on an sco_conn that was concurrently freed:</p>
<p>BUG: KASAN: slab-use-after-free in sco_conn_hold_unless_zero+0xbe/0x160
    Write of size 4 by task kworker/u17:0
    Workqueue: hci0 hci_rx_work
    Call Trace:
     sco_conn_hold_unless_zero+0xbe/0x160
     sco_recv_scodata+0x13f/0x490
     hci_rx_work+0x3af/0x730</p>
<p>kref_get_unless_zero() only guards against a zero refcount, not against
the backing memory already being freed.</p>
<p>Give hcon-&gt;sco_data an actual reference on the sco_conn it points to, so
the object cannot be freed while the pointer is still installed, and only
clear and drop it from sco_conn_del(), which runs under hdev-&gt;lock (its
callers, sco_connect_cfm() and sco_disconn_cfm(), hold it). The reader in
sco_recv_scodata() also takes hdev-&gt;lock, so the store and the read are
now serialised: the RX pat…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99011"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jp44-3rrh-3mww</id>
    <title>GHSA-jp44-3rrh-3mww</title>
    <updated>2026-11-17T10:33:35.732780+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: SCO: serialise sco_conn lifetime against sco_recv_scodata()</p>
<p>sco_recv_scodata() upgrades the weak hcon-&gt;sco_data back-pointer to a
strong reference under hdev-&gt;lock:</p>
<p>hci_dev_lock(hdev);
    hcon = hci_conn_hash_lookup_handle(hdev, handle);
    ...
    conn = sco_conn_hold_unless_zero(hcon-&gt;sco_data);
    hci_dev_unlock(hdev);</p>
<p>but the pointer is cleared from the other side without that lock. When
the last sco_conn reference is dropped, sco_conn_free() ran</p>
<p>conn-&gt;hcon-&gt;sco_data = NULL;</p>
<p>with no hdev-&gt;lock held, so the RX path could read hcon-&gt;sco_data and
call kref_get_unless_zero() on an sco_conn that was concurrently freed:</p>
<p>BUG: KASAN: slab-use-after-free in sco_conn_hold_unless_zero+0xbe/0x160
    Write of size 4 by task kworker/u17:0
    Workqueue: hci0 hci_rx_work
    Call Trace:
     sco_conn_hold_unless_zero+0xbe/0x160
     sco_recv_scodata+0x13f/0x490
     hci_rx_work+0x3af/0x730</p>
<p>kref_get_unless_zero() only guards against a zero refcount, not against
the backing memory already being freed.</p>
<p>Give hcon-&gt;sco_data an actual reference on the sco_conn it points to, so
the object cannot be freed while the pointer is still installed, and only
clear and drop it from sco_conn_del(), which runs under hdev-&gt;lock (its
callers, sco_connect_cfm() and sco_disconn_cfm(), hold it). The reader in
sco_recv_scodata() also takes hdev-&gt;lock, so the store and the read are
now serialised: the RX pat…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jp44-3rrh-3mww"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99011</id>
    <title>msrc_CVE-2026-99011 — Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata()</title>
    <updated>2026-11-17T10:33:35.732821+00:00</updated>
    <content>msrc_CVE-2026-99011</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99011"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99011</id>
    <title>UBUNTU-CVE-2026-99011</title>
    <updated>2026-11-17T10:33:35.732838+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 130 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() sco_recv_scodata() upgrades the weak hcon-&gt;sco_data back-pointer to a strong reference under hdev-&gt;lock:     hci_dev_lock(hdev);     hcon = hci_conn_hash_lookup_handle(hdev, handle);     ...     conn = sco_conn_hold_unless_zero(hcon-&gt;sco_data);     hci_dev_unlock(hdev); but the pointer is cleared from the other side without that lock. When the last sco_conn reference is dropped, sco_conn_free() ran     conn-&gt;hcon-&gt;sco_data = NULL; with no hdev-&gt;lock held, so the RX path could read hcon-&gt;sco_data and call kref_get_unless_zero() on an sco_conn that was concurrently freed:     BUG: KASAN: slab-use-after-free in sco_conn_hold_unless_zero+0xbe/0x160     Write of size 4 by task kworker/u17:0     Workqueue: hci0 hci_rx_work     Call Trace:      sco_conn_hold_unless_zero+0xbe/0x160      sco_recv_scodata+0x13f/0x490      hci_rx_work+0x3af/0x730 kref_get_unless_zero() only guards against a zero refcount, not against the backing memory already being freed. Give hcon-&gt;sco_data an actual reference on the sco_conn it points to, so the object cannot be freed while the pointer is still installed, and only clear and drop it from sco_conn_del(), which runs under hdev-&gt;lock (its callers, sco_connect_cfm() and sco_disconn_cfm(), hold it). The reader in sco_recv_scodata() also takes hdev-&gt;lock, so the store and the read are now serialised: the RX path either…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99011"/>
  </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:33:35.733018+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>
