Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38711, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < 9d5012ffe14120f978ee34aef4df3d6cb026b7c4
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < ac98d54630d5b52e3f684d872f0d82c06c418ea9
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < 1e858a7a51c7b8b009d8f246de7ceb7743b44a71
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < 814cfdb6358d9b84fcbec9918c8f938cc096a43a
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < a7dddd62578c2eb6cb28b8835556a121b5157323
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < a726fef6d7d4cfc365d3434e3916dbfe78991a33
    • affected 0626e6641f6b467447c81dd7678a69c66f7746cf – < d5fc1400a34b4ea5e8f2ce296ea12bf8c8421694
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38711 badge
[![CVE-2025-38711](https://cveledger.app/badge/CVE-2025-38711.svg)](https://cveledger.app/cve/CVE-2025-38711)

Record last updated .