CVE-2025-38347: f2fs: fix to do sanity check on ino and xnid
Published Jul 10, 2025
·Updated
f2fs: fix to do sanity check on ino and xnid
Affected Software
12 affected componentsFixes available
Linux Kernel
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.92.2-2
Linux Linux kernel>=3.8<5.4.297
Linux Linux kernel>=5.5<5.10.241
Linux Linux kernel>=5.11<5.15.190
Linux Linux kernel>=5.16<6.1.149
Linux Linux kernel>=6.2<6.6.95
Linux Linux kernel>=6.7<6.12.35
Linux Linux kernel>=6.13<6.15.4
Debian Debian Linux=11.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Jul 10, 2025
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
Description
Data Sourced
via NVD·09:15 AM
RemedyDescriptionSeverityAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-38347?
The severity of CVE-2025-38347 is classified as medium due to potential system instability issues.
2
How do I fix CVE-2025-38347?
To fix CVE-2025-38347, you should update to the latest version of the Linux kernel that includes the patch.
3
What type of vulnerability is CVE-2025-38347?
CVE-2025-38347 is related to a bug in the f2fs file system implementation of the Linux kernel.
4
Which systems are affected by CVE-2025-38347?
CVE-2025-38347 affects all versions of the Linux kernel that do not include the fix for the f2fs file system.
5
What can happen if CVE-2025-38347 is exploited?
If CVE-2025-38347 is exploited, it may lead to system crashes or significant performance degradation.