CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes
Published Sep 11, 2025
·Updated
btrfs: do not allow relocation of partially dropped subvolumes
Affected Software
17 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.96.2-2
Linux Linux kernel>=5.11.1<5.15.190
Linux Linux kernel>=5.16<6.1.149
Linux Linux kernel>=6.2<6.6.103
Linux Linux kernel>=6.7<6.12.43
Linux Linux kernel>=6.13<6.15.11
Linux Linux kernel>=6.16<6.16.2
Linux Linux kernel=5.11
Linux Linux kernel=5.11-rc3
Linux Linux kernel=5.11-rc4
Linux Linux kernel=5.11-rc5
Linux Linux kernel=5.11-rc6
Linux Linux kernel=5.11-rc7
Linux Linux kernel=6.17-rc1
Debian Debian Linux=11.0
Microsoft cbl2 kernel 5.15.186.1-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel (btrfs)to a version that resolves this vulnerability.Patch 8d488a8c7ba2
Event History
Sep 11, 2025
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
DescriptionSeverity
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityAffected Software
Sep 13, 2025
Data Sourced
via Microsoft·01:04 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-39738?
CVE-2025-39738 is classified as a medium severity vulnerability in the Linux kernel.
2
How do I fix CVE-2025-39738?
To fix CVE-2025-39738, ensure that you update your Linux kernel to the latest stable version that includes the patch.
3
What is the impact of CVE-2025-39738?
The impact of CVE-2025-39738 can lead to transaction aborts during the balancing of Btrfs file systems, affecting data integrity.
4
Which versions of the Linux kernel are affected by CVE-2025-39738?
CVE-2025-39738 affects specific versions of the Linux kernel prior to the patch being applied.
5
Is CVE-2025-39738 remotely exploitable?
CVE-2025-39738 is not considered remotely exploitable as it requires local access to trigger the issue.