CVE-2025-38333
BaseFortify
Publication date: 2025-07-10
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 | 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 file system, specifically in the get_new_segment() function. It involves an inconsistency detected between free_segmap and free_secmap, which are data structures tracking free segments and sections. The fix ensures that when such an inconsistency is detected, the function records the error in the super block and stops further processing instead of continuing to use the problematic segment. This prevents potential errors or corruption related to segment allocation.
How can this vulnerability impact me? :
If exploited or triggered, this vulnerability could lead to file system errors or corruption due to improper handling of segment allocation in the f2fs file system. This might result in data loss, system instability, or crashes when the kernel attempts to allocate new segments incorrectly.
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 warning messages related to f2fs, specifically messages containing 'WARNING: CPU' and references to 'new_curseg' or 'get_new_segment()' failures in the f2fs filesystem code. You can use commands like 'dmesg | grep f2fs' or 'journalctl -k | grep f2fs' to look for such warnings.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this f2fs vulnerability is fixed. Since the issue is resolved by a fix in get_new_segment(), applying the latest kernel patches or upgrading to the fixed kernel version is recommended to prevent the inconsistent segment status issue.