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

10 affected componentsFixes available
Linux Linux kernel
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
Microsoft azl3 kernel 6.6.92.2-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade btrfs (Linux kernel) to a version that resolves this vulnerability.

    Patch btrfs: fix a race between renames and directory logging
  2. Configuration

    Pin the log root during renames before removing the old name to prevent the race between rename and directory inode logging that can lead to file loss.

    btrfs log replay/rename handling pin log root during renames before removing the old name = enabled

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
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203