<?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>Fri, 02 Oct 2026 18:32:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09633</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09633</link>
      <description>bdu:2026-09633</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09633</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>cnvd-2025-10177</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2025-10177</link>
      <description>cnvd-2025-10177</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2025-10177</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49909</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49909</link>
      <description>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49909</guid>
    </item>
    <item>
      <title>GHSA-2f6p-9573-fp98</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2f6p-9573-fp98</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del()&lt;/p&gt;
&lt;p&gt;When l2cap_recv_frame() is invoked to receive data, and the cid is
L2CAP_CID_A2MP, if the channel does not exist, it will create a channel.
However, after a channel is created, the hold operation of the channel
is not performed. In this case, the value of channel reference counting
is 1. As a result, after hci_error_reset() is triggered, l2cap_conn_del()
invokes the close hook function of A2MP to release the channel. Then
 l2cap_chan_unlock(chan) will trigger UAF issue.&lt;/p&gt;
&lt;p&gt;The process is as follows:
Receive data:
l2cap_data_channel()
    a2mp_channel_create()  ---&amp;gt;channel ref is 2
    l2cap_chan_put()       ---&amp;gt;channel ref is 1&lt;/p&gt;
&lt;p&gt;Triger event:
    hci_error_reset()
        hci_dev_do_close()
        ...
        l2cap_disconn_cfm()
            l2cap_conn_del()
                l2cap_chan_hold()    ---&amp;gt;channel ref is 2
                l2cap_chan_del()     ---&amp;gt;channel ref is 1
                a2mp_chan_close_cb() ---&amp;gt;channel ref is 0, release channel
                l2cap_chan_unlock()  ---&amp;gt;UAF of channel&lt;/p&gt;
&lt;p&gt;The detailed Call Trace is as follows:
BUG: KASAN: use-after-free in __mutex_unlock_slowpath+0xa6/0x5e0
Read of size 8 at addr ffff8880160664b8 by task kworker/u11:1/7593
Workqueue: hci0 hci_error_reset
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xcd/0x134
 print_report.cold+0x2ba/0x719
 kasan_report+0xb1/0x1e0
 kasan_check_range+0x140/0x190
 __mutex_unlock_slow…&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 use-after-free in l2cap_conn_del()&lt;/p&gt;
&lt;p&gt;When l2cap_recv_frame() is invoked to receive data, and the cid is
L2CAP_CID_A2MP, if the channel does not exist, it will create a channel.
However, after a channel is created, the hold operation of the channel
is not performed. In this case, the value of channel reference counting
is 1. As a result, after hci_error_reset() is triggered, l2cap_conn_del()
invokes the close hook function of A2MP to release the channel. Then
 l2cap_chan_unlock(chan) will trigger UAF issue.&lt;/p&gt;
&lt;p&gt;The process is as follows:
Receive data:
l2cap_data_channel()
    a2mp_channel_create()  ---&amp;gt;channel ref is 2
    l2cap_chan_put()       ---&amp;gt;channel ref is 1&lt;/p&gt;
&lt;p&gt;Triger event:
    hci_error_reset()
        hci_dev_do_close()
        ...
        l2cap_disconn_cfm()
            l2cap_conn_del()
                l2cap_chan_hold()    ---&amp;gt;channel ref is 2
                l2cap_chan_del()     ---&amp;gt;channel ref is 1
                a2mp_chan_close_cb() ---&amp;gt;channel ref is 0, release channel
                l2cap_chan_unlock()  ---&amp;gt;UAF of channel&lt;/p&gt;
&lt;p&gt;The detailed Call Trace is as follows:
BUG: KASAN: use-after-free in __mutex_unlock_slowpath+0xa6/0x5e0
Read of size 8 at addr ffff8880160664b8 by task kworker/u11:1/7593
Workqueue: hci0 hci_error_reset
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0xcd/0x134
 print_report.cold+0x2ba/0x719
 kasan_report+0xb1/0x1e0
 kasan_check_range+0x140/0x190
 __mutex_unlock_slow…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2f6p-9573-fp98</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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-2025:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49909</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49909</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, 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, Ubuntu:Pro:16.04:LTS: linux-kvm and 136 more&lt;/p&gt;
&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, 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, Ubuntu:Pro:16.04:LTS: linux-kvm and 136 more&lt;/p&gt;
&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49909</guid>
    </item>
  </channel>
</rss>
