CVE-2025-39884
Last modified
CVE-2025-39884 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix subvolume deletion lockup caused by inodes xarray race There is a race condition between inode eviction and inode caching that can cause a live struct btrfs_inode to be missing from the root->inodes xarray. Specifically, there is a window during evict() between the inode being unhashed and deleted from the xarray. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix subvolume deletion lockup caused by inodes xarray race There is a race condition between inode eviction and inode caching that can cause a live struct btrfs_inode to be missing from the root->inodes xarray. Specifically, there is a window during evict() between the inode being unhashed and deleted from the xarray. If btrfs_iget() is called for the same inode in that window, it will be recreated and inserted into the xarray, but then eviction will delete the new entry, leaving nothing in the xarray: Thread 1 Thread 2 --------------------------------------------------------------- evict() remove_inode_hash() btrfs_iget_path() btrfs_iget_locked() btrfs_read_locked_inode() btrfs_add_inode_to_root() destroy_inode() btrfs_destroy_inode() btrfs_del_inode_from_root() __xa_erase In turn, this can cause issues for subvolume deletion. Specifically, if an inode is in this lost state, and all other inodes are evicted, then btrfs_del_inode_from_root() will call btrfs_add_dead_root() prematurely. If the lost inode has a delayed_node attached to it, then when btrfs_clean_one_deleted_snapshot() calls btrfs_kill_all_delayed_nodes(), it will loop forever because the delayed_nodes xarray will never become empty (unless memory pressure forces the inode out). We saw this manifest as soft lockups in production. Fix it by only deleting the xarray entry if it matches the given inode (using __xa_cmpxchg()).
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.11, < 6.12.48 | — |
| Linux | Linux Kernel | >= 6.13, < 6.16.8 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-39884?
How severe is CVE-2025-39884?
How do I fix CVE-2025-39884?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39879In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3988A vulnerability classified as critical has been found in TOT…8.8
- CVE-2025-39880In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39881In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39882In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39883In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39885In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39886In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39887In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39888In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39889In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3989A vulnerability classified as critical was found in TOTOLINK…8.8
Are you affected by CVE-2025-39884?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
