Microsoft · ext4: don't cache extent during splitting extent
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 06:59 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 2 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
AI-suggested
Users should monitor Microsoft Security Response Center updates for any forthcoming patches or recommendations.
Description
CVE-2026-45912 is a vulnerability related to the ext4 filesystem implementation, specifically concerning caching behavior during extent splitting. The available information is limited and does not provide technical details beyond the title or describe exploitation methods or impacts. There is no CVSS score or detailed vendor advisory content available to clarify the severity or remediation status. No known exploits in the wild have been reported. The affected products include Microsoft and Azure Linux 3.0 versions. Patch status is not confirmed, and no official fix or mitigation guidance is provided.