<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T20:31:54.180763+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38244</id>
    <title>CVE-2025-38244 — smb: client: fix potential deadlock when reconnecting channels</title>
    <updated>2026-10-03T20:31:54.355310+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>smb: client: fix potential deadlock when reconnecting channels</p>
<p>Fix cifs_signal_cifsd_for_reconnect() to take the correct lock order
and prevent the following deadlock from happening</p>
<p>======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc3-build2+ #1301 Tainted: G S      W
------------------------------------------------------
cifsd/6055 is trying to acquire lock:
ffff88810ad56038 (&amp;tcp_ses-&gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200</p>
<p>but task is already holding lock:
ffff888119c64330 (&amp;ret_buf-&gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200</p>
<p>which lock already depends on the new lock.</p>
<p>the existing dependency chain (in reverse order) is:</p>
<p>-&gt; #2 (&amp;ret_buf-&gt;chan_lock){+.+.}-{3:3}:
       validate_chain+0x1cf/0x270
       __lock_acquire+0x60e/0x780
       lock_acquire.part.0+0xb4/0x1f0
       _raw_spin_lock+0x2f/0x40
       cifs_setup_session+0x81/0x4b0
       cifs_get_smb_ses+0x771/0x900
       cifs_mount_get_session+0x7e/0x170
       cifs_mount+0x92/0x2d0
       cifs_smb3_do_mount+0x161/0x460
       smb3_get_tree+0x55/0x90
       vfs_get_tree+0x46/0x180
       do_new_mount+0x1b0/0x2e0
       path_mount+0x6ee/0x740
       do_mount+0x98/0xe0
       __do_sys_mount+0x148/0x180
       do_syscall_64+0xa4/0x260
       entry_SYSCALL_64_after_hwframe+0x76/0x7e</p>
<p>-&gt; #1 (&amp;ret_buf-&gt;ses_lock){+.+.}-{3:3}:…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38244"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-7798-1</id>
    <title>USN-7798-1 — linux-azure vulnerabilities</title>
    <updated>2026-10-03T20:31:54.355468+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:25.04: linux-azure</p>
<p>Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network drivers;
  - SMB network file system;
  - Packet sockets;
  - Network traffic control;
  - VMware vSockets driver;
  - XFRM subsystem;
(CVE-2025-38244, CVE-2025-38477, CVE-2025-38617, CVE-2025-38683,
CVE-2025-38618, CVE-2025-38500)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-7798-1"/>
  </entry>
</feed>
