VDB

CVE-2025-38338

CVE-2025-38338 PUBLISHED

fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio()

Reported by linux · Published July 10, 2025

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12-modules-extraAmazon Linux6.12.35-55.103.amzn2023
python3-perf6.12Amazon Linux6.12.35-55.103.amzn2023
kernel-libbpfAmazon Linux6.12.35-55.103.amzn2023
perf6.12Amazon Linux6.12.35-55.103.amzn2023
linux_kernellinux6.15.4, 6.12.35, 6.6.95

Affected products

VendorProductVersions
LinuxLinux000dbe0bec058cbf2ca9e156e4a5584f5158b0f9, 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9, 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9
LinuxLinux6.4, 0, 6.6.95
amazon:2023kernel6.12-modules-extra0
amazon:2023python3-perf6.120
amazon:2023kernel-libbpf0
amazon:2023perf6.120
linuxlinux_kernel6.4, 6.4, 6.4
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-modules-extra-common0
LinuxLinux000dbe0bec058cbf2ca9e156e4a5584f5158b0f9, 6.15.4, 6.16
amazon:2023kernel-libbpf-static0
amazon:2023kernel6.120
amazon:2023kernel-devel0
amazon:2023kernel-tools0
amazon:2023kernel-livepatch-6.12.35-55.1030
amazon:2023kernel-tools-devel0
amazon:2023bpftool0
amazon:2023kernel-headers0

Timeline

  • Jul 9, 2025 CVE Published
  • Jul 10, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 11, 2025 PoC Published (36 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (133 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (138 in total, the first dated here)
  • Jun 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-38338
vulnetix vdb fixes CVE-2025-38338

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38338/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›