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-39734Revert "fs/ntfs3: Replace inode_trylock with inode_lock"

Description

In the Linux kernel, the following vulnerability has been resolved: Revert "fs/ntfs3: Replace inode_trylock with inode_lock" This reverts commit 69505fe98f198ee813898cbcaf6770949636430b. Initially, conditional lock acquisition was removed to fix an xfstest bug that was observed during internal testing. The deadlock reported by syzbot is resolved by reintroducing conditional acquisition. The xfstest bug no longer occurs on kernel version 6.16-rc1 during internal testing. I assume that changes in other modules may have contributed to this.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 9 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-39734, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.15% · top 95% of all CVEs (12 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 e3e3b3eb54feaf6400800812c8d0f95a7213923d – < bec8109f957a6e193e52d1728799994c8005ca83
    • affected 7a498fc945080bccc25fdc36f1d663798441158b – < 1903a6c1f2818154f6bc87bceaaecafa92b6ac5c
    • affected 53173e3865acb06f3e86c703696510c12fecc612 – < a936be9b5f51c4d23f66fb673e9068c6b08104a4
    • affected 69505fe98f198ee813898cbcaf6770949636430b – < b356ee013a79e7e3147bfe065de376706c5d2ee9
    • affected 69505fe98f198ee813898cbcaf6770949636430b – < 7ce6f83ca9d52c9245b7a017466fc4baa1241b0b
    • affected 69505fe98f198ee813898cbcaf6770949636430b – < bd20733746263acaaf2a21881665db27ee4303d5
    • affected 69505fe98f198ee813898cbcaf6770949636430b – < a49f0abd8959048af18c6c690b065eb0d65b2d21
    • affected d5ad80aabd5a76a5de52b7663b1f3223dd01ea38
    • affected 5.15.165 – < 5.15.190
    • affected 6.1.103 – < 6.1.148
    • affected 6.6.44 – < 6.6.102
    • affected 6.10.3 – < 6.11
  • Linux · Linux

    • affected 6.11
    • unaffected < 6.11
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .