CVE-2025-39825

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-09-16. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

smb: client: fix race with concurrent opens in rename(2)

Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as well as marking all existing open handles as deleted to prevent them from deferring closes, which increases the race window for potential concurrent opens on the target file.

Fix this by unhashing the dentry in advance to prevent any concurrent opens on the target.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 16, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

smb: client: fix race with concurrent opens in rename(2) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d84291fc7453df7881a970716f8256273aca5747
generic

smb: client: fix race with concurrent opens in rename(2) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/289f945acb20b9b54fe4d13895e44aa58965ddb2
generic

smb: client: fix race with concurrent opens in rename(2) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9991af5e09924f6f3b3e6996a5e09f9504b4358
generic

smb: client: fix race with concurrent opens in rename(2) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24b9ed739c8c5b464d983e12cf308982f3ae93c2
generic

smb: client: fix race with concurrent opens in rename(2) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c9e7de284da0be5b44dbe79d71573f9f7f9b144c

Patch Availability(23)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)6.1.153-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (43 versions)6.1.153-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+16.12.48-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (60 versions)6.16.5-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 4× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 152 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-07 11:17 UTCOSV refresh
  3. 2026-09-06 13:46 UTCEPSS rescore
  4. 2026-09-04 05:05 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-09-01 04:38 UTCEPSS rescore
  7. 2026-08-30 19:16 UTCEPSS rescore
  8. 2026-08-30 01:21 UTCEPSS rescore
  9. 2026-08-28 21:40 UTCEPSS rescore
  10. 2026-08-27 14:24 UTCEPSS rescore
  11. 2026-08-26 14:45 UTCEPSS rescore
  12. 2026-08-25 13:48 UTCEPSS rescore
  13. 2026-08-21 23:48 UTCEPSS rescore
  14. 2026-08-20 22:54 UTCEPSS rescore
  15. 2026-08-20 20:31 UTCOSV refresh
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:47 UTCEPSS rescore
  19. 2026-08-17 13:46 UTCEPSS rescore
  20. 2026-08-16 14:55 UTCEPSS rescore
  21. 2026-08-16 02:13 UTCEPSS rescore
  22. 2026-08-15 01:29 UTCEPSS rescore
  23. 2026-08-13 21:59 UTCEPSS rescore
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 16:36 UTCEPSS rescore
  2. 2026-08-07 16:26 UTCEPSS rescore
  3. 2026-08-06 13:46 UTCEPSS rescore
  4. 2026-08-05 12:57 UTCEG score recompute
  5. 2026-08-05 12:57 UTCVendor advisory
  6. 2026-08-05 12:57 UTCGHSA enrichment
  7. 2026-08-04 10:37 UTCEPSS rescore
  8. 2026-08-03 10:35 UTCEPSS rescore
  9. 2026-08-02 02:26 UTCEPSS rescore
  10. 2026-08-01 04:15 UTCEPSS rescore
  11. 2026-07-30 16:27 UTCEPSS rescore
  12. 2026-07-30 06:53 UTCEG score recompute
  13. 2026-07-30 06:53 UTCVendor advisory
  14. 2026-07-30 06:53 UTCGHSA enrichment
  15. 2026-07-30 06:24 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  16. 2026-07-28 15:35 UTCEPSS rescore
  17. 2026-07-27 11:09 UTCOSV refresh
  18. 2026-07-25 14:17 UTCEPSS rescore
  19. 2026-07-25 14:17 UTCEPSS rescore
  20. 2026-07-24 14:17 UTCEPSS rescore
  21. 2026-07-23 02:55 UTCEG score recompute
  22. 2026-07-22 14:07 UTCEPSS rescore
  23. 2026-07-22 14:07 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:07 UTCEPSS rescore
  26. 2026-07-19 14:30 UTCEPSS rescore
  27. 2026-07-19 14:30 UTCEPSS rescore
  28. 2026-07-18 10:04 UTCEPSS rescore
  29. 2026-07-18 10:04 UTCEPSS rescore
  30. 2026-07-16 17:02 UTCEPSS rescore
  31. 2026-07-15 16:57 UTCEPSS rescore
  32. 2026-07-15 16:57 UTCEPSS rescore
  33. 2026-07-15 01:59 UTCEPSS rescore
  34. 2026-07-15 01:59 UTCEPSS rescore
  35. 2026-07-13 22:29 UTCEPSS rescore
  36. 2026-07-13 22:29 UTCEPSS rescore
  37. 2026-07-12 05:46 UTCEPSS rescore
  38. 2026-07-10 05:54 UTCOSV refresh
  39. 2026-07-09 19:09 UTCEPSS rescore
  40. 2026-07-09 19:09 UTCEPSS rescore
  41. 2026-07-05 02:30 UTCEPSS rescore
  42. 2026-07-01 15:06 UTCEPSS rescore
  43. 2026-07-01 15:06 UTCEPSS rescore
  44. 2026-06-30 23:22 UTCEPSS rescore
  45. 2026-06-30 23:22 UTCEPSS rescore
  46. 2026-06-28 14:07 UTCEPSS rescore
  47. 2026-06-28 14:07 UTCEPSS rescore
  48. 2026-06-28 04:55 UTCEPSS rescore
  49. 2026-06-28 04:55 UTCEPSS rescore
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-25 13:49 UTCEPSS rescore
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-24 14:04 UTCEPSS rescore
  55. 2026-06-24 14:04 UTCEPSS rescore
  56. 2026-06-23 21:32 UTCEPSS rescore
  57. 2026-06-23 21:32 UTCEPSS rescore
  58. 2026-06-22 14:25 UTCEPSS rescore
  59. 2026-06-22 14:25 UTCEPSS rescore
  60. 2026-06-21 16:19 UTCOSV refresh
  61. 2026-06-21 01:59 UTCEPSS rescore
  62. 2026-06-21 01:59 UTCEPSS rescore
  63. 2026-06-18 17:52 UTCEPSS rescore
  64. 2026-06-18 17:52 UTCEPSS rescore
  65. 2026-06-17 17:52 UTCEPSS rescore
  66. 2026-06-16 17:52 UTCEPSS rescore
  67. 2026-06-16 17:52 UTCEPSS rescore
  68. 2026-06-14 23:18 UTCMITRE cvelistV5
  69. 2026-06-14 23:17 UTCEPSS rescore
  70. 2026-06-13 23:00 UTCEPSS rescore
  71. 2026-06-12 23:11 UTCEPSS rescore
  72. 2026-06-11 14:00 UTCEPSS rescore
  73. 2026-06-10 22:18 UTCEPSS rescore
  74. 2026-06-10 13:22 UTCEPSS rescore
  75. 2026-06-08 14:16 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-39825?
CVE-2025-39825 is a medium vulnerability published on September 16, 2025. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix race with concurrent opens in rename(2) Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as well as marking all…
When was CVE-2025-39825 disclosed?
CVE-2025-39825 was first published in the National Vulnerability Database on September 16, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39825 actively exploited?
CVE-2025-39825 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2025-39825?
CVE-2025-39825 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2025-39825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39825, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-39825

Explore →

Is Your Infrastructure Affected by CVE-2025-39825?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.