<?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 03:16:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-04544</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04544</link>
      <description>bdu:2024-04544</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04544</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-36013</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-36013</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-2024-36013</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>EUVD-2026-345743</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345743</link>
      <description>EUVD-2026-345743</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345743</guid>
    </item>
    <item>
      <title>fkie_cve-2024-36013</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-36013</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
  │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan
  │ __l2cap_chan_add(conn, chan);
  │   l2cap_chan_hold(chan);
  │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)
  └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);
    chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free&lt;/p&gt;
&lt;p&gt;[free]
l2cap_conn_del
┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
│ foreach chan in conn-&amp;gt;chan_l:            ... (2)
│   l2cap_chan_put(chan);
│     l2cap_chan_destroy
│       kfree(chan)               ... (3) &amp;lt;- chan freed
└ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: slab-use-after-free in instrument_atomic_read
include/linux/instrumented.h:68 [inline]
BUG: KASAN: slab-use-after-free in _test_bit
include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0
net/bluetooth/l2cap_core.c:4260
Read of s…&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: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
  │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan
  │ __l2cap_chan_add(conn, chan);
  │   l2cap_chan_hold(chan);
  │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)
  └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);
    chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free&lt;/p&gt;
&lt;p&gt;[free]
l2cap_conn_del
┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
│ foreach chan in conn-&amp;gt;chan_l:            ... (2)
│   l2cap_chan_put(chan);
│     l2cap_chan_destroy
│       kfree(chan)               ... (3) &amp;lt;- chan freed
└ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: slab-use-after-free in instrument_atomic_read
include/linux/instrumented.h:68 [inline]
BUG: KASAN: slab-use-after-free in _test_bit
include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0
net/bluetooth/l2cap_core.c:4260
Read of s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-36013</guid>
    </item>
    <item>
      <title>GHSA-f835-w392-m6qf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f835-w392-m6qf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
  │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan
  │ __l2cap_chan_add(conn, chan);
  │   l2cap_chan_hold(chan);
  │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)
  └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);
    chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free&lt;/p&gt;
&lt;p&gt;[free]
l2cap_conn_del
┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
│ foreach chan in conn-&amp;gt;chan_l:            ... (2)
│   l2cap_chan_put(chan);
│     l2cap_chan_destroy
│       kfree(chan)               ... (3) &amp;lt;- chan freed
└ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: slab-use-after-free in instrument_atomic_read
include/linux/instrumented.h:68 [inline]
BUG: KASAN: slab-use-after-free in _test_bit
include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0
net/bluetooth/l2cap_core.c:4260
Read of s…&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: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
  │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan
  │ __l2cap_chan_add(conn, chan);
  │   l2cap_chan_hold(chan);
  │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)
  └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);
    chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free&lt;/p&gt;
&lt;p&gt;[free]
l2cap_conn_del
┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);
│ foreach chan in conn-&amp;gt;chan_l:            ... (2)
│   l2cap_chan_put(chan);
│     l2cap_chan_destroy
│       kfree(chan)               ... (3) &amp;lt;- chan freed
└ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: slab-use-after-free in instrument_atomic_read
include/linux/instrumented.h:68 [inline]
BUG: KASAN: slab-use-after-free in _test_bit
include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0
net/bluetooth/l2cap_core.c:4260
Read of s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f835-w392-m6qf</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-36013 — Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-36013</link>
      <description>msrc_CVE-2024-36013</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-36013</guid>
    </item>
    <item>
      <title>OESA-2025-1078 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1078</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1078</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2135-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2135-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-2024:2135-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36013</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-36013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 186 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect() Extend a critical section to prevent chan from early freeing. Also make the l2cap_connect() return type void. Nothing is using the returned value but it is ugly to return a potentially freed pointer. Making it void will help with backports because earlier kernels did use the return value. Now the compile will break for kernels where this patch is not a complete fix. Call stack summary: [use] l2cap_bredr_sig_cmd   l2cap_connect   ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);   │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan   │ __l2cap_chan_add(conn, chan);   │   l2cap_chan_hold(chan);   │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)   └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);     chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free [free] l2cap_conn_del ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock); │ foreach chan in conn-&amp;gt;chan_l:            ... (2) │   l2cap_chan_put(chan); │     l2cap_chan_destroy │       kfree(chan)               ... (3) &amp;lt;- chan freed └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock); ================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read include/linux/instrumented.h:68 [inline] BUG: KASAN: slab-use-after-free in _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0 net/bluetooth/l2cap_core.c:4260 Read of size 8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 186 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect() Extend a critical section to prevent chan from early freeing. Also make the l2cap_connect() return type void. Nothing is using the returned value but it is ugly to return a potentially freed pointer. Making it void will help with backports because earlier kernels did use the return value. Now the compile will break for kernels where this patch is not a complete fix. Call stack summary: [use] l2cap_bredr_sig_cmd   l2cap_connect   ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock);   │ chan = pchan-&amp;gt;ops-&amp;gt;new_connection(pchan); &amp;lt;- alloc chan   │ __l2cap_chan_add(conn, chan);   │   l2cap_chan_hold(chan);   │   list_add(&amp;amp;chan-&amp;gt;list, &amp;amp;conn-&amp;gt;chan_l);   ... (1)   └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock);     chan-&amp;gt;conf_state              ... (4) &amp;lt;- use after free [free] l2cap_conn_del ┌ mutex_lock(&amp;amp;conn-&amp;gt;chan_lock); │ foreach chan in conn-&amp;gt;chan_l:            ... (2) │   l2cap_chan_put(chan); │     l2cap_chan_destroy │       kfree(chan)               ... (3) &amp;lt;- chan freed └ mutex_unlock(&amp;amp;conn-&amp;gt;chan_lock); ================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read include/linux/instrumented.h:68 [inline] BUG: KASAN: slab-use-after-free in _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] BUG: KASAN: slab-use-after-free in l2cap_connect+0xa67/0x11a0 net/bluetooth/l2cap_core.c:4260 Read of size 8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-36013</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1227 — Linux Kernel (Bluetooth): Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1227</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in der Bluetooth-Komponente des Linux Kernels ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in der Bluetooth-Komponente des Linux Kernels ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1227</guid>
    </item>
  </channel>
</rss>
