CVE-2025-38626: f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
Published Aug 22, 2025
·Updated
f2fs: fix to trigger foreground gc during f2fsmapblocks() in lfs mode
Affected Software
7 affected componentsFixes available
Linux Kernel=
Linux Linux kernel>=4.8<6.6.102
Linux Linux kernel>=6.7<6.12.42
Linux Linux kernel>=6.13<6.15.10
Linux Linux kernel>=6.16<6.16.1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Remediation
Event History
Aug 22, 2025
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·10:39 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·10:39 PM
Affected Software
Updated
via Microsoft·10:39 PM
SeverityAffected Software
Updated
via Microsoft·10:39 PM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-38626?
CVE-2025-38626 is classified as a high severity vulnerability due to its potential to cause system panic.
2
How do I fix CVE-2025-38626?
To fix CVE-2025-38626, update the Linux kernel to the patched version that resolves the f2fs foreground GC trigger issue.
3
What does CVE-2025-38626 affect?
CVE-2025-38626 affects the Linux kernel specifically when using the f2fs file system with the 'mode=lfs' mount option.
4
What happens if CVE-2025-38626 is exploited?
If exploited, CVE-2025-38626 can lead to a kernel BUG and result in system panic.
5
When was CVE-2025-38626 resolved?
CVE-2025-38626 was resolved with updates made available in the Linux kernel community in response to the identified vulnerability.