<?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 08:00:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80914</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80914</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-80914</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367514</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367514</link>
      <description>EUVD-2026-367514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367514</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80914</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80914</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready&lt;/p&gt;
&lt;p&gt;iso_conn_ready() looks up the BIS listener socket with iso_get_sock(),
which takes a reference, and then, without re-checking its state,
creates a child socket from it:&lt;/p&gt;
&lt;p&gt;parent = iso_get_sock(hdev, ...);
    if (!parent)
        return;&lt;/p&gt;
&lt;p&gt;lock_sock(parent);
    sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);
    ...
    iso_chan_add(conn, sk, parent);
    ...
    release_sock(parent);
    sock_put(parent);&lt;/p&gt;
&lt;p&gt;If the listener socket is closed concurrently, between iso_get_sock()
and lock_sock(), the reference taken by iso_get_sock() may be the last
one: the close path drops the link-list reference, and once
iso_conn_ready() drops its own reference at the end of the function the
socket is freed.  The child socket, however, is already linked to the
freed parent, and a later disconnect of the child runs iso_chan_del()
-&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer
into the freed accept queue (a use-after-free).  The same dangling
pointer is also dereferenced through parent-&amp;gt;***() in
iso_chan_del().&lt;/p&gt;
&lt;p&gt;Fix it the same way the connected (non-BIS) path was fixed in commit
0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;):
after taking the socket lock, re-check that the parent is still a
listening, alive socket, and bail out otherwise.&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: ISO: fix use-after-free of listener socket in iso_conn_ready&lt;/p&gt;
&lt;p&gt;iso_conn_ready() looks up the BIS listener socket with iso_get_sock(),
which takes a reference, and then, without re-checking its state,
creates a child socket from it:&lt;/p&gt;
&lt;p&gt;parent = iso_get_sock(hdev, ...);
    if (!parent)
        return;&lt;/p&gt;
&lt;p&gt;lock_sock(parent);
    sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);
    ...
    iso_chan_add(conn, sk, parent);
    ...
    release_sock(parent);
    sock_put(parent);&lt;/p&gt;
&lt;p&gt;If the listener socket is closed concurrently, between iso_get_sock()
and lock_sock(), the reference taken by iso_get_sock() may be the last
one: the close path drops the link-list reference, and once
iso_conn_ready() drops its own reference at the end of the function the
socket is freed.  The child socket, however, is already linked to the
freed parent, and a later disconnect of the child runs iso_chan_del()
-&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer
into the freed accept queue (a use-after-free).  The same dangling
pointer is also dereferenced through parent-&amp;gt;***() in
iso_chan_del().&lt;/p&gt;
&lt;p&gt;Fix it the same way the connected (non-BIS) path was fixed in commit
0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;):
after taking the socket lock, re-check that the parent is still a
listening, alive socket, and bail out otherwise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80914</guid>
    </item>
    <item>
      <title>GHSA-xmw2-vj5q-xhxr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xmw2-vj5q-xhxr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready&lt;/p&gt;
&lt;p&gt;iso_conn_ready() looks up the BIS listener socket with iso_get_sock(),
which takes a reference, and then, without re-checking its state,
creates a child socket from it:&lt;/p&gt;
&lt;p&gt;parent = iso_get_sock(hdev, ...);
    if (!parent)
        return;&lt;/p&gt;
&lt;p&gt;lock_sock(parent);
    sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);
    ...
    iso_chan_add(conn, sk, parent);
    ...
    release_sock(parent);
    sock_put(parent);&lt;/p&gt;
&lt;p&gt;If the listener socket is closed concurrently, between iso_get_sock()
and lock_sock(), the reference taken by iso_get_sock() may be the last
one: the close path drops the link-list reference, and once
iso_conn_ready() drops its own reference at the end of the function the
socket is freed.  The child socket, however, is already linked to the
freed parent, and a later disconnect of the child runs iso_chan_del()
-&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer
into the freed accept queue (a use-after-free).  The same dangling
pointer is also dereferenced through parent-&amp;gt;***() in
iso_chan_del().&lt;/p&gt;
&lt;p&gt;Fix it the same way the connected (non-BIS) path was fixed in commit
0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;):
after taking the socket lock, re-check that the parent is still a
listening, alive socket, and bail out otherwise.&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: ISO: fix use-after-free of listener socket in iso_conn_ready&lt;/p&gt;
&lt;p&gt;iso_conn_ready() looks up the BIS listener socket with iso_get_sock(),
which takes a reference, and then, without re-checking its state,
creates a child socket from it:&lt;/p&gt;
&lt;p&gt;parent = iso_get_sock(hdev, ...);
    if (!parent)
        return;&lt;/p&gt;
&lt;p&gt;lock_sock(parent);
    sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);
    ...
    iso_chan_add(conn, sk, parent);
    ...
    release_sock(parent);
    sock_put(parent);&lt;/p&gt;
&lt;p&gt;If the listener socket is closed concurrently, between iso_get_sock()
and lock_sock(), the reference taken by iso_get_sock() may be the last
one: the close path drops the link-list reference, and once
iso_conn_ready() drops its own reference at the end of the function the
socket is freed.  The child socket, however, is already linked to the
freed parent, and a later disconnect of the child runs iso_chan_del()
-&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer
into the freed accept queue (a use-after-free).  The same dangling
pointer is also dereferenced through parent-&amp;gt;***() in
iso_chan_del().&lt;/p&gt;
&lt;p&gt;Fix it the same way the connected (non-BIS) path was fixed in commit
0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;):
after taking the socket lock, re-check that the parent is still a
listening, alive socket, and bail out otherwise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xmw2-vj5q-xhxr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-80914 — Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-80914</link>
      <description>msrc_CVE-2026-80914</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-80914</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11773-1 — kernel-devel-7.2.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80914</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80914</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready iso_conn_ready() looks up the BIS listener socket with iso_get_sock(), which takes a reference, and then, without re-checking its state, creates a child socket from it:     parent = iso_get_sock(hdev, ...);     if (!parent)         return;     lock_sock(parent);     sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);     ...     iso_chan_add(conn, sk, parent);     ...     release_sock(parent);     sock_put(parent); If the listener socket is closed concurrently, between iso_get_sock() and lock_sock(), the reference taken by iso_get_sock() may be the last one: the close path drops the link-list reference, and once iso_conn_ready() drops its own reference at the end of the function the socket is freed.  The child socket, however, is already linked to the freed parent, and a later disconnect of the child runs iso_chan_del() -&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer into the freed accept queue (a use-after-free).  The same dangling pointer is also dereferenced through parent-&amp;gt;***() in iso_chan_del(). Fix it the same way the connected (non-BIS) path was fixed in commit 0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;): after taking the socket lock, re-check that the parent is still a listening, alive socket, and bail out otherwise.&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready iso_conn_ready() looks up the BIS listener socket with iso_get_sock(), which takes a reference, and then, without re-checking its state, creates a child socket from it:     parent = iso_get_sock(hdev, ...);     if (!parent)         return;     lock_sock(parent);     sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...);     ...     iso_chan_add(conn, sk, parent);     ...     release_sock(parent);     sock_put(parent); If the listener socket is closed concurrently, between iso_get_sock() and lock_sock(), the reference taken by iso_get_sock() may be the last one: the close path drops the link-list reference, and once iso_conn_ready() drops its own reference at the end of the function the socket is freed.  The child socket, however, is already linked to the freed parent, and a later disconnect of the child runs iso_chan_del() -&amp;gt; bt_accept_unlink(), which dereferences the dangling parent pointer into the freed accept queue (a use-after-free).  The same dangling pointer is also dereferenced through parent-&amp;gt;***() in iso_chan_del(). Fix it the same way the connected (non-BIS) path was fixed in commit 0d255e63fcf3 (&amp;#34;Bluetooth: ISO: hold sk properly in iso_conn_ready&amp;#34;): after taking the socket lock, re-check that the parent is still a listening, alive socket, and bail out otherwise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80914</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3294 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3294</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3294</guid>
    </item>
  </channel>
</rss>
