Back to CVE records
Medium 5.5Published May 27, 2026

CVE-2026-45912ext4: don't cache extent during splitting extent

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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. In the future, we will add checks when caching extents, which will trigger a warning. Therefore, Do not cache extents that are being split.

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Undergoing Analysis
Record last updated
May 30, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 107a7bd31ac003e42c0f966aa8e5b26947de6024 before 8302b5b4aacdbb378f7b1216bb2ee782b5142415; from 107a7bd31ac003e42c0f966aa8e5b26947de6024 before 692103feca376ae4298c92aa8828015d20f1d87b; 107a7bd31ac003e42c0f966aa8e5b26947de6024 builds before 4c2d9dac4d328244f9365b0a1fa27ec802821820; 107a7bd31ac003e42c0f966aa8e5b26947de6024 builds before 93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036; from 107a7bd31ac003e42c0f966aa8e5b26947de6024 before 96007fd3c106aea773c1afae2d6f64cceb6da208; 107a7bd31ac003e42c0f966aa8e5b26947de6024 builds before 5b1f4290453314e11cd8e15c7baa8a9b76c19b23; 107a7bd31ac003e42c0f966aa8e5b26947de6024 builds before 9a2b95cdaf07785e2739199037bd9c0863ccc1be; 107a7bd31ac003e42c0f966aa8e5b26947de6024 builds before 8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79
CNA record
linux linux_kernel
linux:linux_kernel
from 3.12 before 5.10.252; from 5.11 before 5.15.202; from 5.16 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.14; from 6.19 before 6.19.4
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.