CVE-2025-39868
BaseFortify
Publication date: 2025-09-23
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.15 (inc) to 6.16.8 (exc) |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
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 the erofs filesystem runtime warning on truncate_folio_batch_exceptionals(). Applying the patch that ensures all pages are idle prior to filesystem unmount, as done for xfs and ext4 and now applied to erofs, will resolve the issue.
Can you explain this vulnerability to me?
This vulnerability is a runtime warning in the Linux kernel related to the erofs filesystem. It occurs in the function truncate_folio_batch_exceptionals(), which was missing a fix that ensures all pages are idle before the filesystem is unmounted. The issue was introduced by a commit that added a warning to check if all DAX entries were removed during unmounting, which was fixed for other filesystems like xfs and ext4 but missed for erofs. This could cause a runtime warning and potentially unstable behavior during filesystem unmount operations.
How can this vulnerability impact me? :
The impact of this vulnerability is primarily a runtime warning during the unmounting of the erofs filesystem, which could indicate improper handling of memory pages. While it may not directly lead to a security breach, it could cause system instability or crashes during filesystem unmount operations, potentially affecting 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 should check the kernel logs for warnings similar to: "WARNING: CPU: ... at mm/truncate.c:89 truncate_folio_batch_exceptionals". You can use the command: dmesg | grep truncate_folio_batch_exceptionals to search for this warning in the kernel ring buffer.