Skip to content
Heist/ feed
Back to feed
UnratedFix available

ext4: don't cache extent during splitting extent

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: ext4: don't cache extent during splitting extent Caching extents during the splitting process is risky, as it may result in stale extents remaining in the status tree. Moreover, in most cases, the corresponding extent block entries are likely already cached before the split happens, making caching here not particularly useful. Assume we have an unwritten extent, and then DIO writes the first half. [UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range First, when ext4_split_extent_at() splits this extent, it truncates the existing extent and then inserts a new one. During this process, this extent status entry may be shrunk, and calls to ext4_find_extent() and ext4_cache_extents() may occur, which could potentially insert the truncated range as a hole into the extent status tree. After the split is completed, this hole is not replaced with the correct status. [UUUUUUU|UUUUUUUU] on-disk extent U: unwritten extent [UUUUUUU|HHHHHHHH] extent status tree H: hole Then, the outer calling functions will not correct this remaining hole extent either. Finally, if we perform a delayed buffer write on this latter part, it will re-insert the delayed extent and cause an error in space accounting. In adition, if the unwritten extent cache is not shrunk during the splitting, ext4_cache_extents() also conflicts with existing extents when caching extents.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.252, 5.15.202, 6.1.165, 6.12.75, 6.18.14, 6.19.4, 6.6.128
CVEs
CVE-2026-45912
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 01:49 UTC · Revision 1

Source evidence

ext4: don't cache extent during splitting extent

core-osv · Original source

Published 27 May 2026, 12:17 UTC

In the Linux kernel, the following vulnerability has been resolved: ext4: don't cache extent during splitting extent Caching extents during the splitting process is risky, as it may result in stale extents remaining in the status tree. Moreover, in most cases, the corresponding extent block entries are likely already cached before the split happens, making caching here not particularly useful. Assume we have an unwritten extent, and then DIO writes the first half. [UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range First, when ext4_split_extent_at() splits this extent, it truncates the existing extent and then inserts a new one. During this process, this extent status entry may be shrunk, and calls to ext4_find_extent() and ext4_cache_extents() may occur, which could potentially insert the truncated range as a hole into the extent status tree. After the split is completed, this hole is not replaced with the correct status. [UUUUUUU|UUUUUUUU] on-disk extent U: unwritten extent [UUUUUUU|HHHHHHHH] extent status tree H: hole Then, the outer calling functions will not correct this remaining hole extent either. Finally, if we perform a delayed buffer write on this latter part, it will re-insert the delayed extent and cause an error in space accounting. In adition, if the unwritten extent cache is not shrunk during the splitting, ext4_cache_extents() also conflicts with existing extents when caching extents.

osv:CVE-2026-45912

Kernel

Fixed versions: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14, 6.19.4

Complete source record
{
  "id": "0eda4eb2262e527ffd7e8a6468f48aceee8017c856a10ea7389b92ad1e5d78b0",
  "url": "https://osv.dev/vulnerability/CVE-2026-45912",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ext4: don't cache extent during splitting extent",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: ext4: don't cache extent during splitting extent Caching extents during the splitting process is risky, as it may result in stale extents remaining in the status tree. Moreover, in most cases, the corresponding extent block entries are likely already cached before the split happens, making caching here not particularly useful. Assume we have an unwritten extent, and then DIO writes the first half. [UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range First, when ext4_split_extent_at() splits this extent, it truncates the existing extent and then inserts a new one. During this process, this extent status entry may be shrunk, and calls to ext4_find_extent() and ext4_cache_extents() may occur, which could potentially insert the truncated range as a hole into the extent status tree. After the split is completed, this hole is not replaced with the correct status. [UUUUUUU|UUUUUUUU] on-disk extent U: unwritten extent [UUUUUUU|HHHHHHHH] extent status tree H: hole Then, the outer calling functions will not correct this remaining hole extent either. Finally, if we perform a delayed buffer write on this latter part, it will re-insert the delayed extent and cause an error in space accounting. In adition, if the unwritten extent cache is not shrunk during the splitting, ext4_cache_extents() also conflicts with existing extents when caching extents. ",
    "evidence": "osv:CVE-2026-45912",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.252",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.202",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.165",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.128",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.75",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.14",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-45912",
      "aliases": [
        "CVE-2026-45912"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "107a7bd31ac003e42c0f966aa8e5b26947de6024"
                },
                {
                  "fixed": "8302b5b4aacdbb378f7b1216bb2ee782b5142415"
                },
                {
                  "fixed": "692103feca376ae4298c92aa8828015d20f1d87b"
                },
                {
                  "fixed": "4c2d9dac4d328244f9365b0a1fa27ec802821820"
                },
                {
                  "fixed": "93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036"
                },
                {
                  "fixed": "96007fd3c106aea773c1afae2d6f64cceb6da208"
                },
                {
                  "fixed": "5b1f4290453314e11cd8e15c7baa8a9b76c19b23"
                },
                {
                  "fixed": "9a2b95cdaf07785e2739199037bd9c0863ccc1be"
                },
                {
                  "fixed": "8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45912.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "3.12.0"
                },
                {
                  "fixed": "5.10.252"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.202"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.165"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.128"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.75"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.14"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45912.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:45.969282325Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/4c2d9dac4d328244f9365b0a1fa27ec802821820",
        "https://git.kernel.org/stable/c/5b1f4290453314e11cd8e15c7baa8a9b76c19b23",
        "https://git.kernel.org/stable/c/692103feca376ae4298c92aa8828015d20f1d87b",
        "https://git.kernel.org/stable/c/8302b5b4aacdbb378f7b1216bb2ee782b5142415",
        "https://git.kernel.org/stable/c/8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79",
        "https://git.kernel.org/stable/c/93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036",
        "https://git.kernel.org/stable/c/96007fd3c106aea773c1afae2d6f64cceb6da208",
        "https://git.kernel.org/stable/c/9a2b95cdaf07785e2739199037bd9c0863ccc1be",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45912.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-45912",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45912.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-45912",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 514004,
  "published_at": "2026-05-27T12:17:27.805+00:00"
}