CVE-2025-38357
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a runtime warning issue in the Linux kernel's fuse filesystem related to the function truncate_folio_batch_exceptionals(). The warning occurs because the filesystem did not properly remove all DAX entries before unmounting, which was a fix previously applied to other filesystems like xfs and ext4 but missed for fuse. The fix ensures that all pages are idle prior to filesystem unmount, preventing the runtime warning.
How can this vulnerability impact me? :
This vulnerability causes a runtime warning in the kernel when unmounting a fuse filesystem, which could lead to instability or unexpected behavior during filesystem operations. While it does not describe a direct security exploit, such warnings can indicate potential issues in filesystem handling that might affect system reliability.
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 the specific runtime warning message related to truncate_folio_batch_exceptionals(). You can check the kernel logs for the warning using the command: dmesg | grep 'truncate_folio_batch_exceptionals'. This will help identify if the WARN_ON_ONCE warning has been triggered, indicating the presence of the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that fixes the runtime warning in the fuse filesystem, as done in the Linux kernel commit 0e2f80afcfa6. Until the patch is applied, monitoring for the warning and avoiding unmounting filesystems that use fuse under conditions that trigger this warning can reduce impact. Updating the Linux kernel to a version that includes this fix is the recommended step.