<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 13:03:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31408 — Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31408</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: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold&lt;/p&gt;
&lt;p&gt;sco_recv_frame() reads conn-&amp;gt;sk under sco_conn_lock() but immediately
releases the lock without holding a reference to the socket. A concurrent
close() can free the socket between the lock release and the subsequent
sk-&amp;gt;sk_state access, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Other functions in the same file (sco_sock_timeout(), sco_conn_del())
correctly use sco_sock_hold() to safely hold a reference under the lock.&lt;/p&gt;
&lt;p&gt;Fix by using sco_sock_hold() to take a reference before releasing the
lock, and adding sock_put() on all exit paths.&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: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold&lt;/p&gt;
&lt;p&gt;sco_recv_frame() reads conn-&amp;gt;sk under sco_conn_lock() but immediately
releases the lock without holding a reference to the socket. A concurrent
close() can free the socket between the lock release and the subsequent
sk-&amp;gt;sk_state access, resulting in a use-after-free.&lt;/p&gt;
&lt;p&gt;Other functions in the same file (sco_sock_timeout(), sco_conn_del())
correctly use sco_sock_hold() to safely hold a reference under the lock.&lt;/p&gt;
&lt;p&gt;Fix by using sco_sock_hold() to take a reference before releasing the
lock, and adding sock_put() on all exit paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31408</guid>
    </item>
  </channel>
</rss>
