CVE-2025-38365: btrfs: fix a race between renames and directory logging
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 2088895d5903082bb9021770b919e733c57edbc1, 3ca864de852bc91007b32d2a0d48993724f4abad, 51bd363c7010d033d3334daf457c824484bf9bf0; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
- Severity is disputed: the assigning authority (CNA) scores it 9.1, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 2088895d5903082bb9021770b919e733c57edbc1, 3ca864de852bc91007b32d2a0d48993724f4abad, 51bd363c7010d033d3334daf457c824484bf9bf0; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix a race between renames and directory logging We have a race between a rename and directory inode logging that if it happens and we crash/power fail before the rename completes, the next time the filesystem is mounted, the log replay code will end up deleting the file that was being renamed. This is best explained following a step by step analysis of an interleaving of steps that lead into this situation. Consider the initial conditions: 1) We are at transaction N; 2) We have directories A and B created in a past transaction (< N); 3) We have inode X corresponding to a file that has 2 hardlinks, one in directory A and the other in directory B, so we'll name them as "A/foo_link1" and "B/foo_link2". Both hard links were persisted in a past transaction (< N); 4) We have inode Y corresponding to a file that as a single hard link and is located in directory A, we'll name it as "A/bar". This file was also persisted in a past transaction (< N). The steps leading to a file loss are the following and for all of them we are under transaction N: 1) Link "A/foo_link1" is removed, so inode's X last_unlink_trans field is updated to N, through btrfs_unlink() -> btrfs_record_unlink_dir(); 2) Task A starts a rename for inode Y, with the goal of renaming from "A/bar" to "A/baz", so we enter btrfs_rename(); 3) Task A inserts the new BTRFS_INODE_REF_KEY for inode Y by calling btrfs_insert_inode_ref(); 4) Because the rename happens in the same directory, we don't set the last_unlink_trans field of directoty A's inode to the current transaction id, that is, we don't cal btrfs_record_unlink_dir(); 5) Task A then removes the entries from directory A (BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items) when calling __btrfs_unlink_inode() (actually the dir index item is added as a delayed item, but the effect is the same); 6) Now before task A adds the new entry "A/baz" to directory A by calling btrfs_add_link(), another task, task B is logging inode X; 7) Task B starts a fsync of inode X and after logging inode X, at btrfs_log_inode_parent() it calls btrfs_log_all_parents(), since inode X has a last_unlink_trans value of N, set at in step 1; 8) At btrfs_log_all_parents() we search for all parent directories of inode X using the commit root, so we find directories A and B and log them. Bu when logging direct A, we don't have a dir index item for inode Y anymore, neither the old name "A/bar" nor for the new name "A/baz" since the rename has deleted the old name but has not yet inserted the new name - task A hasn't called yet btrfs_add_link() to do that. Note that logging directory A doesn't fallback to a transaction commit because its last_unlink_trans has a lower value than the current transaction's id (see step 4); 9) Task B finishes logging directories A and B and gets back to btrfs_sync_file() where it calls btrfs_sync_log() to persist the log tree; 10) Task B successfully persisted the log tree, btrfs_sync_log() completed with success, and a power failure happened. We have a log tree without any directory entry for inode Y, so the log replay code deletes the entry for inode Y, name "A/bar", from the subvolume tree since it doesn't exist in the log tree and the log tree is authorative for its index (we logged a BTRFS_DIR_LOG_INDEX_KEY item that covers the index range for the dentry that corresponds to "A/bar"). Since there's no other hard link for inode Y and the log replay code deletes the name "A/bar", the file is lost. The issue wouldn't happen if task B synced the log only after task A called btrfs_log_new_name(), which would update the log with the new name for inode Y ("A/bar"). Fix this by pinning the log root during renames before removing the old directory entry, and unpinning af ---truncated---
- Published
- Jul 25, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-362
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 9.1
- 4.4 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 259c4b96d78dda8477a3ac21d6b3cf0eb9f75c8b and later · before 51bd363c7010d033d3334daf457c824484bf9bf0affected · git
- 259c4b96d78dda8477a3ac21d6b3cf0eb9f75c8b and later · before aeeae8feeaae4445a86f9815273e81f902dc1f5baffected · git
- 259c4b96d78dda8477a3ac21d6b3cf0eb9f75c8b and later · before 2088895d5903082bb9021770b919e733c57edbc1affected · git
- 259c4b96d78dda8477a3ac21d6b3cf0eb9f75c8b and later · before 8c6874646c21bd820cf475e2874e62c133954023affected · git
- 259c4b96d78dda8477a3ac21d6b3cf0eb9f75c8b and later · before 3ca864de852bc91007b32d2a0d48993724f4abadaffected · git
- before 5.18not affected · semver
- 6.1.143 and later · up to and including 6.1.*not affected · semver
- 6.6.96 and later · up to and including 6.6.*not affected · semver
- 6.12.36 and later · up to and including 6.12.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.18 and later · before 6.1.143
- linux linux kernel6.2 and later · before 6.6.96
- linux linux kernel6.7 and later · before 6.12.36
- linux linux kernel6.13 and later · before 6.15.5
- linux linux kernel6.16
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.37-1 | 6.12.37-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38361Jul 25, 2025 · drm/amd/display: Check dce_hwseq before dereferencing it31Monitor
- ← EarlierCVE-2025-38362Jul 25, 2025 · drm/amd/display: Add null pointer check for get_first_active_display()22Monitor
- Later →CVE-2025-38366Jul 25, 2025 · LoongArch: KVM: Check validity of "num_cpu" from user space31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2088895d5903082bb9021770b919e733c57edbc1 | Vendor (CNA) |
| Linux Linux | 3ca864de852bc91007b32d2a0d48993724f4abad | Vendor (CNA) |
| Linux Linux | 51bd363c7010d033d3334daf457c824484bf9bf0 | Vendor (CNA) |
| Linux Linux | 8c6874646c21bd820cf475e2874e62c133954023 | Vendor (CNA) |
| Linux Linux | aeeae8feeaae4445a86f9815273e81f902dc1f5b | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3ca864de852bc91007b32d2a0d48993724f4abad
- git.kernel.org/stable/c/51bd363c7010d033d3334daf457c824484bf9bf0
- git.kernel.org/stable/c/8c6874646c21bd820cf475e2874e62c133954023
- git.kernel.org/stable/c/aeeae8feeaae4445a86f9815273e81f902dc1f5b
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.