<?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>Sun, 04 Oct 2026 18:45:30 +0000</lastBuildDate>
    <item>
      <title>UBUNTU-CVE-2023-52757</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52757</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential deadlock when releasing mids All release_mid() callers seem to hold a reference of @mid so there is no need to call kref_put(&amp;amp;mid-&amp;gt;refcount, __release_mid) under @server-&amp;gt;mid_lock spinlock.  If they don&amp;#39;t, then an use-after-free bug would have occurred anyways. By getting rid of such spinlock also fixes a potential deadlock as shown below CPU 0                                CPU 1 ------------------------------------------------------------------ cifs_demultiplex_thread()            cifs_debug_data_proc_show()  release_mid()   spin_lock(&amp;amp;server-&amp;gt;mid_lock);                                      spin_lock(&amp;amp;cifs_tcp_ses_lock) 				      spin_lock(&amp;amp;server-&amp;gt;mid_lock)   __release_mid()    smb2_find_smb_tcon()     spin_lock(&amp;amp;cifs_tcp_ses_lock) *deadlock*&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: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-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential deadlock when releasing mids All release_mid() callers seem to hold a reference of @mid so there is no need to call kref_put(&amp;amp;mid-&amp;gt;refcount, __release_mid) under @server-&amp;gt;mid_lock spinlock.  If they don&amp;#39;t, then an use-after-free bug would have occurred anyways. By getting rid of such spinlock also fixes a potential deadlock as shown below CPU 0                                CPU 1 ------------------------------------------------------------------ cifs_demultiplex_thread()            cifs_debug_data_proc_show()  release_mid()   spin_lock(&amp;amp;server-&amp;gt;mid_lock);                                      spin_lock(&amp;amp;cifs_tcp_ses_lock) 				      spin_lock(&amp;amp;server-&amp;gt;mid_lock)   __release_mid()    smb2_find_smb_tcon()     spin_lock(&amp;amp;cifs_tcp_ses_lock) *deadlock*&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52757</guid>
    </item>
  </channel>
</rss>
