CVE-2026-45912: Linux kernel · ext4: don't cache extent during splitting extent
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 692103feca376ae4298c92aa8828015d20f1d87b : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:05 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in 692103feca376ae4298c92aa8828015d20f1d87b, 96007fd3c106aea773c1afae2d6f64cceb6da208, 8302b5b4aacdbb378f7b1216bb2ee782b5142415 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel versions identified by the provided commit hashes. Users should update to a kernel version that includes these fixes to mitigate the issue. No additional mitigation steps are indicated or necessary beyond applying the official fix.
Description
A vulnerability in the Linux kernel ext4 filesystem involves improper caching of extents during the splitting process. This can lead to stale or incorrect extent status entries, causing errors in space accounting when delayed writes occur. The issue arises because extents being split are cached incorrectly, potentially leaving holes in the extent status tree that are not corrected.
References
- git.kernel.org/stable/c/8302b5b4aacdbb378f7b1216bb2ee782b5142415 (opens in a new tab)
- git.kernel.org/stable/c/692103feca376ae4298c92aa8828015d20f1d87b (opens in a new tab)
- git.kernel.org/stable/c/4c2d9dac4d328244f9365b0a1fa27ec802821820 (opens in a new tab)
- git.kernel.org/stable/c/93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036 (opens in a new tab)
- git.kernel.org/stable/c/96007fd3c106aea773c1afae2d6f64cceb6da208 (opens in a new tab)
- git.kernel.org/stable/c/5b1f4290453314e11cd8e15c7baa8a9b76c19b23 (opens in a new tab)
- git.kernel.org/stable/c/9a2b95cdaf07785e2739199037bd9c0863ccc1be (opens in a new tab)
- git.kernel.org/stable/c/8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79 (opens in a new tab)