CVE-2025-38164
BaseFortify
Publication date: 2025-07-03
Last updated on: 2026-03-25
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) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| 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 in the Linux kernel's F2FS filesystem. It causes inconsistency between the Segment Information Table (SIT) and the Segment Summary Area (SSA) due to the f2fs_gc_range() function attempting to migrate blocks in a segment whose summary block data is still cached and not up to date. This can lead to the filesystem being stopped due to detected inconsistencies.
How can this vulnerability impact me? :
The vulnerability can cause the F2FS filesystem to detect inconsistencies and stop functioning properly, potentially leading to filesystem errors or data access issues during operations like fallocate. This may result in system instability or data unavailability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing error messages related to F2FS filesystem inconsistencies, such as 'Inconsistent segment type in SSA and SIT' and filesystem stoppage messages. Monitoring system logs (e.g., dmesg or /var/log/syslog) for such F2FS error messages can help detect the issue. Specific commands to check logs include: 'dmesg | grep f2fs' or 'journalctl -k | grep f2fs'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the patch fixing the inconsistency between SIT and SSA in the F2FS filesystem. Until then, avoid running workloads that trigger the issue, such as fallocate operations on F2FS filesystems, to prevent filesystem corruption or stoppage.