CVE-2025-38276
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel relates to the fs/dax subsystem where a function called wait_entry_unlocked_exclusive() improperly handles locked entries when scanning. Specifically, the function advances the iterator state prematurely, causing it to skip locked entries that it should wait for. This leads to intermittent warnings and potential issues during filesystem operations, such as truncation on XFS filesystems with FS DAX enabled.
How can this vulnerability impact me? :
The vulnerability can cause filesystem operations to behave incorrectly by skipping locked entries during scans. This may result in warnings, errors, or unexpected behavior during file truncation or other filesystem modifications, potentially affecting system stability or data integrity on systems using FS DAX with XFS.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific kernel warnings related to the issue. Look for warnings similar to the following in your kernel logs: "WARNING: CPU: PID at mm/truncate.c:89 truncate_folio_batch_exceptionals" especially when running workloads involving XFS filesystem with FS DAX enabled. You can check the kernel logs using the command: dmesg | grep -i 'truncate_folio_batch_exceptionals' or dmesg | grep -i 'WARNING'.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Linux kernel to a version that includes the fix for this issue, specifically the commit that addresses the skipping of locked entries when scanning entries in fs/dax. Until the kernel is updated, monitoring for the warning messages and avoiding workloads that trigger this condition on XFS filesystems with FS DAX enabled may reduce exposure.