CVE-2025-39734 json
Revert "fs/ntfs3: Replace inode_trylock with inode_lock"
published 2025-09-07 14 mo ago modified 2026-10-19 20 d ago also EUVD-2025-31496
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.15.190, 6.1.148, 6.6.102, 6.11, 6.12.42, 6.15.10, 6.16.1, 6.17
- linux Debian 12 6.1.148-1
- linux Debian 13 6.12.43-1
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-39734
- linux Ubuntu 22.04 LTS 5.15.0-163.173
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1097.104
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1097.106
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1093.99
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-39734
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/bec8109f957a6e193e52d1728799994c8005ca83 commit
- git.kernel.org/stable/c/1903a6c1f2818154f6bc87bceaaecafa92b6ac5c commit
- git.kernel.org/stable/c/a936be9b5f51c4d23f66fb673e9068c6b08104a4 commit
- git.kernel.org/stable/c/b356ee013a79e7e3147bfe065de376706c5d2ee9 commit
- git.kernel.org/stable/c/7ce6f83ca9d52c9245b7a017466fc4baa1241b0b commit
- git.kernel.org/stable/c/bd20733746263acaaf2a21881665db27ee4303d5 commit
- git.kernel.org/stable/c/a49f0abd8959048af18c6c690b065eb0d65b2d21 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-39734 updated
kernel: Revert "fs/ntfs3: Replace inode_trylock with inode_lock"
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/bec8109f957a6e193e52d1728799994c8005ca83
patch
-
git.kernel.org
/stable/c/1903a6c1f2818154f6bc87bceaaecafa92b6ac5c
patch
-
git.kernel.org
/stable/c/a936be9b5f51c4d23f66fb673e9068c6b08104a4
patch
-
git.kernel.org
/stable/c/b356ee013a79e7e3147bfe065de376706c5d2ee9
patch
-
git.kernel.org
/stable/c/7ce6f83ca9d52c9245b7a017466fc4baa1241b0b
patch
-
git.kernel.org
/stable/c/bd20733746263acaaf2a21881665db27ee4303d5
patch
-
git.kernel.org
/stable/c/a49f0abd8959048af18c6c690b065eb0d65b2d21
patch
-
lists.debian.org
/debian-lts-announce/2025/10/msg00008.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2025-39734
- NVD CVE-2025-39734
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.