<?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, 10 Oct 2026 21:46:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41062 — bluetooth/l2cap: sync sock recv cb and release</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-41062</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bluetooth/l2cap: sync sock recv cb and release&lt;/p&gt;
&lt;p&gt;The problem occurs between the system call to close the sock and hci_rx_work,
where the former releases the sock and the latter accesses it without lock protection.&lt;/p&gt;
&lt;p&gt;CPU0                       CPU1
           ----                       ----
           sock_close                 hci_rx_work
	   l2cap_sock_release         hci_acldata_packet
	   l2cap_sock_kill            l2cap_recv_frame
	   sk_free                    l2cap_conless_channel
	                              l2cap_sock_recv_cb&lt;/p&gt;
&lt;p&gt;If hci_rx_work processes the data that needs to be received before the sock is
closed, then everything is normal; Otherwise, the work thread may access the
released sock when receiving data.&lt;/p&gt;
&lt;p&gt;Add a chan mutex in the rx callback of the sock to achieve synchronization between
the sock release and recv cb.&lt;/p&gt;
&lt;p&gt;Sock is dead, so set chan data to NULL, avoid others use invalid sock pointer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bluetooth/l2cap: sync sock recv cb and release&lt;/p&gt;
&lt;p&gt;The problem occurs between the system call to close the sock and hci_rx_work,
where the former releases the sock and the latter accesses it without lock protection.&lt;/p&gt;
&lt;p&gt;CPU0                       CPU1
           ----                       ----
           sock_close                 hci_rx_work
	   l2cap_sock_release         hci_acldata_packet
	   l2cap_sock_kill            l2cap_recv_frame
	   sk_free                    l2cap_conless_channel
	                              l2cap_sock_recv_cb&lt;/p&gt;
&lt;p&gt;If hci_rx_work processes the data that needs to be received before the sock is
closed, then everything is normal; Otherwise, the work thread may access the
released sock when receiving data.&lt;/p&gt;
&lt;p&gt;Add a chan mutex in the rx callback of the sock to achieve synchronization between
the sock release and recv cb.&lt;/p&gt;
&lt;p&gt;Sock is dead, so set chan data to NULL, avoid others use invalid sock pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-41062</guid>
    </item>
  </channel>
</rss>
