Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23465btrfs: log new dentries when logging parent dir of a conflicting inode

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23465, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < 6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4
    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < 56e72c8b02d982be775d9df025357c152383ee84
    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < f556b1e09d054e31f464c0fd37280c2b5a393fee
    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < 1cf30c73602c69d750c9345c47f2c0e9d0cfb578
    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < 6f5a51969b1deb79aefd2194b48fe7e78e72ff7e
    • affected a3baaf0d786e22fc86295fda9c58ba0dee07599f – < 9573a365ff9ff45da9222d3fe63695ce562beb24
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23465 badge
[![CVE-2026-23465](https://cveledger.app/badge/CVE-2026-23465.svg)](https://cveledger.app/cve/CVE-2026-23465)

Record last updated .