CVE-2025-71069 (GCVE-0-2025-71069)

Vulnerability from cvelistv5 – Published: 2026-01-13 15:31 – Updated: 2026-05-11 21:54
VLAI
Title
f2fs: invalidate dentry cache on failed whiteout creation
Summary
In the Linux kernel, the following vulnerability has been resolved: f2fs: invalidate dentry cache on failed whiteout creation F2FS can mount filesystems with corrupted directory depth values that get runtime-clamped to MAX_DIR_HASH_DEPTH. When RENAME_WHITEOUT operations are performed on such directories, f2fs_rename performs directory modifications (updating target entry and deleting source entry) before attempting to add the whiteout entry via f2fs_add_link. If f2fs_add_link fails due to the corrupted directory structure, the function returns an error to VFS, but the partial directory modifications have already been committed to disk. VFS assumes the entire rename operation failed and does not update the dentry cache, leaving stale mappings. In the error path, VFS does not call d_move() to update the dentry cache. This results in new_dentry still pointing to the old inode (new_inode) which has already had its i_nlink decremented to zero. The stale cache causes subsequent operations to incorrectly reference the freed inode. This causes subsequent operations to use cached dentry information that no longer matches the on-disk state. When a second rename targets the same entry, VFS attempts to decrement i_nlink on the stale inode, which may already have i_nlink=0, triggering a WARNING in drop_nlink(). Example sequence: 1. First rename (RENAME_WHITEOUT): file2 → file1 - f2fs updates file1 entry on disk (points to inode 8) - f2fs deletes file2 entry on disk - f2fs_add_link(whiteout) fails (corrupted directory) - Returns error to VFS - VFS does not call d_move() due to error - VFS cache still has: file1 → inode 7 (stale!) - inode 7 has i_nlink=0 (already decremented) 2. Second rename: file3 → file1 - VFS uses stale cache: file1 → inode 7 - Tries to drop_nlink on inode 7 (i_nlink already 0) - WARNING in drop_nlink() Fix this by explicitly invalidating old_dentry and new_dentry when f2fs_add_link fails during whiteout creation. This forces VFS to refresh from disk on subsequent operations, ensuring cache consistency even when the rename partially succeeds. Reproducer: 1. Mount F2FS image with corrupted i_current_depth 2. renameat2(file2, file1, RENAME_WHITEOUT) 3. renameat2(file3, file1, 0) 4. System triggers WARNING in drop_nlink()
Severity
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < 7f2bae0c881aa1e0a6318756df692cc13df2cc83 (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < 3d95ed8cf980fdfa67a3ab9491357521ae576168 (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < 64587ab4d1f16fc94f70e04fa87b2e3f69f8a7bb (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < 3d65e27e57aaa9d66709fda4cbfb62a87c04a3f5 (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < c89845fae250efdd59c1d4ec60e9e1c652cee4b6 (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < 0dde30753c1e8648665dbe069d814e540ce2fd37 (git)
Affected: 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 , < d33f89b34aa313f50f9a512d58dd288999f246b0 (git)
Create a notification for this product.
Linux Linux Affected: 4.2
Unaffected: 0 , < 4.2 (semver)
Unaffected: 5.10.248 , ≤ 5.10.* (semver)
Unaffected: 5.15.198 , ≤ 5.15.* (semver)
Unaffected: 6.1.160 , ≤ 6.1.* (semver)
Unaffected: 6.6.120 , ≤ 6.6.* (semver)
Unaffected: 6.12.64 , ≤ 6.12.* (semver)
Unaffected: 6.18.3 , ≤ 6.18.* (semver)
Unaffected: 6.19 , ≤ * (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/f2fs/namei.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7f2bae0c881aa1e0a6318756df692cc13df2cc83",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "3d95ed8cf980fdfa67a3ab9491357521ae576168",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "64587ab4d1f16fc94f70e04fa87b2e3f69f8a7bb",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "3d65e27e57aaa9d66709fda4cbfb62a87c04a3f5",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "c89845fae250efdd59c1d4ec60e9e1c652cee4b6",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "0dde30753c1e8648665dbe069d814e540ce2fd37",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            },
            {
              "lessThan": "d33f89b34aa313f50f9a512d58dd288999f246b0",
              "status": "affected",
              "version": "7e01e7ad746bc8198a8b46163ddc73a1c7d22339",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/namei.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.2"
            },
            {
              "lessThan": "4.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.248",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.198",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.160",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.120",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.248",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.198",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.160",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.120",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.64",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.3",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19",
                  "versionStartIncluding": "4.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: invalidate dentry cache on failed whiteout creation\n\nF2FS can mount filesystems with corrupted directory depth values that\nget runtime-clamped to MAX_DIR_HASH_DEPTH. When RENAME_WHITEOUT\noperations are performed on such directories, f2fs_rename performs\ndirectory modifications (updating target entry and deleting source\nentry) before attempting to add the whiteout entry via f2fs_add_link.\n\nIf f2fs_add_link fails due to the corrupted directory structure, the\nfunction returns an error to VFS, but the partial directory\nmodifications have already been committed to disk. VFS assumes the\nentire rename operation failed and does not update the dentry cache,\nleaving stale mappings.\n\nIn the error path, VFS does not call d_move() to update the dentry\ncache. This results in new_dentry still pointing to the old inode\n(new_inode) which has already had its i_nlink decremented to zero.\nThe stale cache causes subsequent operations to incorrectly reference\nthe freed inode.\n\nThis causes subsequent operations to use cached dentry information that\nno longer matches the on-disk state. When a second rename targets the\nsame entry, VFS attempts to decrement i_nlink on the stale inode, which\nmay already have i_nlink=0, triggering a WARNING in drop_nlink().\n\nExample sequence:\n1. First rename (RENAME_WHITEOUT): file2 \u2192 file1\n   - f2fs updates file1 entry on disk (points to inode 8)\n   - f2fs deletes file2 entry on disk\n   - f2fs_add_link(whiteout) fails (corrupted directory)\n   - Returns error to VFS\n   - VFS does not call d_move() due to error\n   - VFS cache still has: file1 \u2192 inode 7 (stale!)\n   - inode 7 has i_nlink=0 (already decremented)\n\n2. Second rename: file3 \u2192 file1\n   - VFS uses stale cache: file1 \u2192 inode 7\n   - Tries to drop_nlink on inode 7 (i_nlink already 0)\n   - WARNING in drop_nlink()\n\nFix this by explicitly invalidating old_dentry and new_dentry when\nf2fs_add_link fails during whiteout creation. This forces VFS to\nrefresh from disk on subsequent operations, ensuring cache consistency\neven when the rename partially succeeds.\n\nReproducer:\n1. Mount F2FS image with corrupted i_current_depth\n2. renameat2(file2, file1, RENAME_WHITEOUT)\n3. renameat2(file3, file1, 0)\n4. System triggers WARNING in drop_nlink()"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T21:54:08.205Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7f2bae0c881aa1e0a6318756df692cc13df2cc83"
        },
        {
          "url": "https://git.kernel.org/stable/c/3d95ed8cf980fdfa67a3ab9491357521ae576168"
        },
        {
          "url": "https://git.kernel.org/stable/c/64587ab4d1f16fc94f70e04fa87b2e3f69f8a7bb"
        },
        {
          "url": "https://git.kernel.org/stable/c/3d65e27e57aaa9d66709fda4cbfb62a87c04a3f5"
        },
        {
          "url": "https://git.kernel.org/stable/c/c89845fae250efdd59c1d4ec60e9e1c652cee4b6"
        },
        {
          "url": "https://git.kernel.org/stable/c/0dde30753c1e8648665dbe069d814e540ce2fd37"
        },
        {
          "url": "https://git.kernel.org/stable/c/d33f89b34aa313f50f9a512d58dd288999f246b0"
        }
      ],
      "title": "f2fs: invalidate dentry cache on failed whiteout creation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-71069",
    "datePublished": "2026-01-13T15:31:23.948Z",
    "dateReserved": "2026-01-13T15:30:19.647Z",
    "dateUpdated": "2026-05-11T21:54:08.205Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-71069",
      "date": "2026-05-27",
      "epss": "0.00068",
      "percentile": "0.21037"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-71069\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-01-13T16:16:06.300\",\"lastModified\":\"2026-01-19T13:16:16.067\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nf2fs: invalidate dentry cache on failed whiteout creation\\n\\nF2FS can mount filesystems with corrupted directory depth values that\\nget runtime-clamped to MAX_DIR_HASH_DEPTH. When RENAME_WHITEOUT\\noperations are performed on such directories, f2fs_rename performs\\ndirectory modifications (updating target entry and deleting source\\nentry) before attempting to add the whiteout entry via f2fs_add_link.\\n\\nIf f2fs_add_link fails due to the corrupted directory structure, the\\nfunction returns an error to VFS, but the partial directory\\nmodifications have already been committed to disk. VFS assumes the\\nentire rename operation failed and does not update the dentry cache,\\nleaving stale mappings.\\n\\nIn the error path, VFS does not call d_move() to update the dentry\\ncache. This results in new_dentry still pointing to the old inode\\n(new_inode) which has already had its i_nlink decremented to zero.\\nThe stale cache causes subsequent operations to incorrectly reference\\nthe freed inode.\\n\\nThis causes subsequent operations to use cached dentry information that\\nno longer matches the on-disk state. When a second rename targets the\\nsame entry, VFS attempts to decrement i_nlink on the stale inode, which\\nmay already have i_nlink=0, triggering a WARNING in drop_nlink().\\n\\nExample sequence:\\n1. First rename (RENAME_WHITEOUT): file2 \u2192 file1\\n   - f2fs updates file1 entry on disk (points to inode 8)\\n   - f2fs deletes file2 entry on disk\\n   - f2fs_add_link(whiteout) fails (corrupted directory)\\n   - Returns error to VFS\\n   - VFS does not call d_move() due to error\\n   - VFS cache still has: file1 \u2192 inode 7 (stale!)\\n   - inode 7 has i_nlink=0 (already decremented)\\n\\n2. Second rename: file3 \u2192 file1\\n   - VFS uses stale cache: file1 \u2192 inode 7\\n   - Tries to drop_nlink on inode 7 (i_nlink already 0)\\n   - WARNING in drop_nlink()\\n\\nFix this by explicitly invalidating old_dentry and new_dentry when\\nf2fs_add_link fails during whiteout creation. This forces VFS to\\nrefresh from disk on subsequent operations, ensuring cache consistency\\neven when the rename partially succeeds.\\n\\nReproducer:\\n1. Mount F2FS image with corrupted i_current_depth\\n2. renameat2(file2, file1, RENAME_WHITEOUT)\\n3. renameat2(file3, file1, 0)\\n4. System triggers WARNING in drop_nlink()\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0dde30753c1e8648665dbe069d814e540ce2fd37\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/3d65e27e57aaa9d66709fda4cbfb62a87c04a3f5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/3d95ed8cf980fdfa67a3ab9491357521ae576168\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/64587ab4d1f16fc94f70e04fa87b2e3f69f8a7bb\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7f2bae0c881aa1e0a6318756df692cc13df2cc83\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c89845fae250efdd59c1d4ec60e9e1c652cee4b6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d33f89b34aa313f50f9a512d58dd288999f246b0\",\"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.