CVE-2025-38260: btrfs: handle csum tree error with rescue=ibadroots correctly
Published Jul 9, 2025
·Updated
btrfs: handle csum tree error with rescue=ibadroots correctly
Affected Software
10 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.17<6.1.143
Linux Linux kernel>=6.2<6.6.96
Linux Linux kernel>=6.7<6.12.36
Linux Linux kernel>=6.13<6.15.5
Linux Linux kernel=6.16-rc1
Linux Linux kernel=6.16-rc2
Linux Linux kernel=6.16-rc3
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.92.2-2
Remediation
Event History
Jul 9, 2025
CVE Published
via MITRE·10:42 AM
Data Sourced
via MITRE·10:42 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-38260?
CVE-2025-38260 is classified with a high severity due to its ability to crash the Linux kernel.
2
How do I fix CVE-2025-38260?
Fix CVE-2025-38260 by updating to the latest version of the Linux kernel where the vulnerability has been patched.
3
What systems are affected by CVE-2025-38260?
CVE-2025-38260 affects Linux kernel versions prior to the resolution, impacting systems using the btrfs filesystem.
4
Can CVE-2025-38260 be exploited remotely?
CVE-2025-38260 requires local access for exploitation, as it involves a kernel crash scenario.
5
What should I do if I am running a vulnerable version related to CVE-2025-38260?
If you are running a vulnerable version related to CVE-2025-38260, you should prioritize upgrading the Linux kernel to eliminate the vulnerability.