CVE-2025-38338fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio()
- 7.8HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio() Sometimes, when a file was read while it was being truncated by another NFS client, the kernel could deadlock because folio_unlock() was called twice, and the second call would XOR back the `PG_locked` flag. Most of the time (depending on the timing of the truncation), nobody notices the problem because folio_unlock() gets called three times, which flips `PG_locked` back off: 1. vfs_read, nfs_read_folio, ... nfs_read_add_folio, nfs_return_empty_folio 2. vfs_read, nfs_read_folio, ... netfs_read_collection, netfs_unlock_abandoned_read_pages 3. vfs_read, ... nfs_do_read_folio, nfs_read_add_folio, nfs_return_empty_folio The problem is that nfs_read_add_folio() is not supposed to unlock the folio if fscache is enabled, and a nfs_netfs_folio_unlock() check is missing in nfs_return_empty_folio(). Rarely this leads to a warning in netfs_read_collection(): ------------[ cut here ]------------ R=0000031c: folio 10 is not locked WARNING: CPU: 0 PID: 29 at fs/netfs/read_collect.c:133 netfs_read_collection+0x7c0/0xf00 [...] Workqueue: events_unbound netfs_read_collection_worker RIP: 0010:netfs_read_collection+0x7c0/0xf00 [...] Call Trace: <TASK> netfs_read_collection_worker+0x67/0x80 process_one_work+0x12e/0x2c0 worker_thread+0x295/0x3a0 Most of the time, however, processes just get stuck forever in folio_wait_bit_common(), waiting for `PG_locked` to disappear, which never happens because nobody is really holding the folio lock.
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 16 months later
· 16 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 – < 14f5549ad163be2c018abc1bb38370fff617a243
- affected 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 – < 5bf0b9eeb0174686f22c2e5b8fb9f47ad25da6f5
- affected 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 – < 1e93b61d3eaa14bfebcc2716ac09d43f3845d420
- affected 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 – < 4c10fa44bc5f700e2ea21de2fbae520ba21f19d9
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.95 – ≤ 6.6.*
- unaffected 6.12.35 – ≤ 6.12.*
- unaffected 6.15.4 – ≤ 6.15.*
- unaffected 6.16 – ≤ *
References
References4
- https://git.kernel.org/stable/c/14f5549ad163be2c018abc1bb38370fff617a243 (opens in a new tab)
- https://git.kernel.org/stable/c/5bf0b9eeb0174686f22c2e5b8fb9f47ad25da6f5 (opens in a new tab)
- https://git.kernel.org/stable/c/1e93b61d3eaa14bfebcc2716ac09d43f3845d420 (opens in a new tab)
- https://git.kernel.org/stable/c/4c10fa44bc5f700e2ea21de2fbae520ba21f19d9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-20908 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38338)Record last updated .