# CVE-2025-38711: smb/server: avoid deadlock when linking with ReplaceIfExists

> A deadlock in the Linux kernel SMB server allows remote attackers to cause a denial of service by triggering a specific file linking operation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** AZL-66872, BELL-CVE-2025-38711, DEBIAN-CVE-2025-38711, GHSA-c3j4-c39c-w5r2, ROOT-OS-DEBIAN-11-CVE-2025-38711, ROOT-OS-DEBIAN-12-CVE-2025-38711, ROOT-OS-UBUNTU-2204-CVE-2025-38711, ROOT-OS-UBUNTU-2404-CVE-2025-38711, UBUNTU-CVE-2025-38711

## What is CVE-2025-38711?

CVE-2025-38711 is a medium-severity vulnerability in Debian Debian Linux, published on 4 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

smb/server: avoid deadlock when linking with ReplaceIfExists

If smb2_create_link() is called with ReplaceIfExists set and the name
does exist then a deadlock will happen.

ksmbd_vfs_kern_path_locked() will return with success and the parent
directory will be locked.  ksmbd_vfs_remove_file() will then remove the
file.  ksmbd_vfs_link() will then be called while the parent is still
locked.  It will try to lock the same parent and will deadlock.

This patch moves the ksmbd_vfs_kern_path_unlock() call to *before*
ksmbd_vfs_link() and then simplifies the code, removing the file_present
flag variable.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-38711?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-38711?

Apply the vendor's patch.

## Is CVE-2025-38711 being exploited?

There is no known exploitation of CVE-2025-38711 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38711 and fix it if it is affected.

What it is: CVE-2025-38711 is a medium-severity vulnerability in Debian Debian Linux, published on 4 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-38711 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-38711/ (Markdown: https://insights.sbomify.com/CVE-2025-38711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38711
- OSV: https://osv.dev/vulnerability/CVE-2025-38711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-38711/
Summaries are generated and may contain mistakes; the official description above is the record.