CVE-2025-38365: btrfs: fix a race between renames and directory logging
Published Jul 25, 2025
·Updated
btrfs: fix a race between renames and directory logging
Affected Software
11 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.92.2-2
Linux Linux kernel>=5.18<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
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 25, 2025
CVE Published
via MITRE·12:47 PM
Data Sourced
via MITRE·12:47 PM
DescriptionSeverity
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-38365?
CVE-2025-38365 is considered a moderate severity vulnerability affecting the Linux kernel.
2
How do I fix CVE-2025-38365?
To fix CVE-2025-38365, update to the patched version of the Linux kernel that addresses this race condition.
3
What systems are affected by CVE-2025-38365?
CVE-2025-38365 affects the Linux kernel, specifically systems utilizing btrfs filesystems.
4
What are the potential impacts of CVE-2025-38365?
CVE-2025-38365 can lead to data loss or corruption if a crash occurs during a rename operation.
5
When was CVE-2025-38365 disclosed?
CVE-2025-38365 was disclosed in 2025, along with guidance on resolving the identified vulnerabilities.