CVE-2026-23465 Details
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: log new dentries when logging parent dir of a conflicting inode If we log the parent directory of a conflicting inode, we are not logging the new dentries of the directory, so when we finish we have the parent directory's inode marked as logged but we did not log its new dentries. As a consequence if the parent directory is explicitly fsynced later and it does not have any new changes since we logged it, the fsync is a no-op and after a power failure the new dentries are missing. Example scenario: $ mkdir foo $ sync $rmdir foo $ mkdir dir1 $ mkdir dir2 # A file with the same name and parent as the directory we just deleted # and was persisted in a past transaction. So the deleted directory's # inode is a conflicting inode of this new file's inode. $ touch foo $ ln foo dir2/link # The fsync on dir2 will log the parent directory (".") because the # conflicting inode (deleted directory) does not exists anymore, but it # it does not log its new dentries (dir1). $ xfs_io -c "fsync" dir2 # This fsync on the parent directory is no-op, since the previous fsync # logged it (but without logging its new dentries). $ xfs_io -c "fsync" . <power failure> # After log replay dir1 is missing. Fix this by ensuring we log new dir dentries whenever we log the parent directory of a no longer existing conflicting inode. A test case for fstests will follow soon.
A vulnerability in the Linux kernel's Btrfs file system has been addressed, concerning the logging of new directory entries (dentries) when the parent directory of a conflicting inode is logged. The issue arises because, while the parent directory's inode is marked as logged, the new dentries are not. This oversight can lead to data loss: if the parent directory is later fsynced and no new changes have been made since it was logged, the fsync operation becomes a no-op. Following a power failure, the newly created dentries may be missing. The vulnerability affects several versions of the Linux kernel.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1cf30c73602c69d750c9345c47f2c0e9d0cfb578 | kernel.org | Patch |
| https://git.kernel.org/stable/c/56e72c8b02d982be775d9df025357c152383ee84 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4 | kernel.org | |
| https://git.kernel.org/stable/c/6f5a51969b1deb79aefd2194b48fe7e78e72ff7e | kernel.org | Patch |
| https://git.kernel.org/stable/c/9573a365ff9ff45da9222d3fe63695ce562beb24 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f556b1e09d054e31f464c0fd37280c2b5a393fee | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.1, < 6.6.130 >= 6.7, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | kernel.org |
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 20, 2026 | Initial Analysis | [email protected] |
| Apr 3, 2026 | New CVE Received | kernel.org |