btrfs: log new dentries when logging parent dir of a conflicting inode
Summary
| CVE | CVE-2026-23465 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-04-03 16:16:33 UTC |
|---|
| Updated | 2026-04-03 16:16:33 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected a3baaf0d786e22fc86295fda9c58ba0dee07599f 56e72c8b02d982be775d9df025357c152383ee84 git |
Not specified |
| CNA |
Linux |
Linux |
affected a3baaf0d786e22fc86295fda9c58ba0dee07599f f556b1e09d054e31f464c0fd37280c2b5a393fee git |
Not specified |
| CNA |
Linux |
Linux |
affected a3baaf0d786e22fc86295fda9c58ba0dee07599f 1cf30c73602c69d750c9345c47f2c0e9d0cfb578 git |
Not specified |
| CNA |
Linux |
Linux |
affected a3baaf0d786e22fc86295fda9c58ba0dee07599f 6f5a51969b1deb79aefd2194b48fe7e78e72ff7e git |
Not specified |
| CNA |
Linux |
Linux |
affected a3baaf0d786e22fc86295fda9c58ba0dee07599f 9573a365ff9ff45da9222d3fe63695ce562beb24 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.1 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.1 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.130 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.78 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.20 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.10 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0-rc5 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/56e72c8b02d982be775d9df025357c152383ee84 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6f5a51969b1deb79aefd2194b48fe7e78e72ff7e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9573a365ff9ff45da9222d3fe63695ce562beb24 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1cf30c73602c69d750c9345c47f2c0e9d0cfb578 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f556b1e09d054e31f464c0fd37280c2b5a393fee |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.
