CVE-2026-23465 (GCVE-0-2026-23465)

Vulnerability from cvelistv5 – Published: 2026-04-03 15:15 – Updated: 2026-04-13 06:07
VLAI?
Title
btrfs: log new dentries when logging parent dir of a conflicting inode
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: a3baaf0d786e22fc86295fda9c58ba0dee07599f , < 56e72c8b02d982be775d9df025357c152383ee84 (git)
Affected: a3baaf0d786e22fc86295fda9c58ba0dee07599f , < f556b1e09d054e31f464c0fd37280c2b5a393fee (git)
Affected: a3baaf0d786e22fc86295fda9c58ba0dee07599f , < 1cf30c73602c69d750c9345c47f2c0e9d0cfb578 (git)
Affected: a3baaf0d786e22fc86295fda9c58ba0dee07599f , < 6f5a51969b1deb79aefd2194b48fe7e78e72ff7e (git)
Affected: a3baaf0d786e22fc86295fda9c58ba0dee07599f , < 9573a365ff9ff45da9222d3fe63695ce562beb24 (git)
Create a notification for this product.
    Linux Linux Affected: 5.1
Unaffected: 0 , < 5.1 (semver)
Unaffected: 6.6.130 , ≤ 6.6.* (semver)
Unaffected: 6.12.78 , ≤ 6.12.* (semver)
Unaffected: 6.18.20 , ≤ 6.18.* (semver)
Unaffected: 6.19.10 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/tree-log.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "56e72c8b02d982be775d9df025357c152383ee84",
              "status": "affected",
              "version": "a3baaf0d786e22fc86295fda9c58ba0dee07599f",
              "versionType": "git"
            },
            {
              "lessThan": "f556b1e09d054e31f464c0fd37280c2b5a393fee",
              "status": "affected",
              "version": "a3baaf0d786e22fc86295fda9c58ba0dee07599f",
              "versionType": "git"
            },
            {
              "lessThan": "1cf30c73602c69d750c9345c47f2c0e9d0cfb578",
              "status": "affected",
              "version": "a3baaf0d786e22fc86295fda9c58ba0dee07599f",
              "versionType": "git"
            },
            {
              "lessThan": "6f5a51969b1deb79aefd2194b48fe7e78e72ff7e",
              "status": "affected",
              "version": "a3baaf0d786e22fc86295fda9c58ba0dee07599f",
              "versionType": "git"
            },
            {
              "lessThan": "9573a365ff9ff45da9222d3fe63695ce562beb24",
              "status": "affected",
              "version": "a3baaf0d786e22fc86295fda9c58ba0dee07599f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/tree-log.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.1"
            },
            {
              "lessThan": "5.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.130",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.78",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.20",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.130",
                  "versionStartIncluding": "5.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.78",
                  "versionStartIncluding": "5.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.20",
                  "versionStartIncluding": "5.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.10",
                  "versionStartIncluding": "5.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "5.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: log new dentries when logging parent dir of a conflicting inode\n\nIf we log the parent directory of a conflicting inode, we are not logging\nthe new dentries of the directory, so when we finish we have the parent\ndirectory\u0027s inode marked as logged but we did not log its new dentries.\nAs a consequence if the parent directory is explicitly fsynced later and\nit does not have any new changes since we logged it, the fsync is a no-op\nand after a power failure the new dentries are missing.\n\nExample scenario:\n\n  $ mkdir foo\n\n  $ sync\n\n  $rmdir foo\n\n  $ mkdir dir1\n  $ mkdir dir2\n\n  # A file with the same name and parent as the directory we just deleted\n  # and was persisted in a past transaction. So the deleted directory\u0027s\n  # inode is a conflicting inode of this new file\u0027s inode.\n  $ touch foo\n\n  $ ln foo dir2/link\n\n  # The fsync on dir2 will log the parent directory (\".\") because the\n  # conflicting inode (deleted directory) does not exists anymore, but it\n  # it does not log its new dentries (dir1).\n  $ xfs_io -c \"fsync\" dir2\n\n  # This fsync on the parent directory is no-op, since the previous fsync\n  # logged it (but without logging its new dentries).\n  $ xfs_io -c \"fsync\" .\n\n  \u003cpower failure\u003e\n\n  # After log replay dir1 is missing.\n\nFix this by ensuring we log new dir dentries whenever we log the parent\ndirectory of a no longer existing conflicting inode.\n\nA test case for fstests will follow soon."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-13T06:07:59.882Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/56e72c8b02d982be775d9df025357c152383ee84"
        },
        {
          "url": "https://git.kernel.org/stable/c/f556b1e09d054e31f464c0fd37280c2b5a393fee"
        },
        {
          "url": "https://git.kernel.org/stable/c/1cf30c73602c69d750c9345c47f2c0e9d0cfb578"
        },
        {
          "url": "https://git.kernel.org/stable/c/6f5a51969b1deb79aefd2194b48fe7e78e72ff7e"
        },
        {
          "url": "https://git.kernel.org/stable/c/9573a365ff9ff45da9222d3fe63695ce562beb24"
        }
      ],
      "title": "btrfs: log new dentries when logging parent dir of a conflicting inode",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23465",
    "datePublished": "2026-04-03T15:15:44.862Z",
    "dateReserved": "2026-01-13T15:37:46.021Z",
    "dateUpdated": "2026-04-13T06:07:59.882Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-23465",
      "date": "2026-05-07",
      "epss": "0.00026",
      "percentile": "0.0733"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-23465\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-04-03T16:16:33.850\",\"lastModified\":\"2026-04-07T13:20:55.200\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nbtrfs: log new dentries when logging parent dir of a conflicting inode\\n\\nIf we log the parent directory of a conflicting inode, we are not logging\\nthe new dentries of the directory, so when we finish we have the parent\\ndirectory\u0027s inode marked as logged but we did not log its new dentries.\\nAs a consequence if the parent directory is explicitly fsynced later and\\nit does not have any new changes since we logged it, the fsync is a no-op\\nand after a power failure the new dentries are missing.\\n\\nExample scenario:\\n\\n  $ mkdir foo\\n\\n  $ sync\\n\\n  $rmdir foo\\n\\n  $ mkdir dir1\\n  $ mkdir dir2\\n\\n  # A file with the same name and parent as the directory we just deleted\\n  # and was persisted in a past transaction. So the deleted directory\u0027s\\n  # inode is a conflicting inode of this new file\u0027s inode.\\n  $ touch foo\\n\\n  $ ln foo dir2/link\\n\\n  # The fsync on dir2 will log the parent directory (\\\".\\\") because the\\n  # conflicting inode (deleted directory) does not exists anymore, but it\\n  # it does not log its new dentries (dir1).\\n  $ xfs_io -c \\\"fsync\\\" dir2\\n\\n  # This fsync on the parent directory is no-op, since the previous fsync\\n  # logged it (but without logging its new dentries).\\n  $ xfs_io -c \\\"fsync\\\" .\\n\\n  \u003cpower failure\u003e\\n\\n  # After log replay dir1 is missing.\\n\\nFix this by ensuring we log new dir dentries whenever we log the parent\\ndirectory of a no longer existing conflicting inode.\\n\\nA test case for fstests will follow soon.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1cf30c73602c69d750c9345c47f2c0e9d0cfb578\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/56e72c8b02d982be775d9df025357c152383ee84\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6f5a51969b1deb79aefd2194b48fe7e78e72ff7e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9573a365ff9ff45da9222d3fe63695ce562beb24\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f556b1e09d054e31f464c0fd37280c2b5a393fee\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.