CVE-2026-98445: Linux kernel · xfs: don't let memory failures leak blocks and kill repairs
Source GCVE Database
Not known to be exploited · fixed in b15c79fca28060fd9c7e77f2c3ebc4ba023974e8 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b15c79fca28060fd9c7e77f2c3ebc4ba023974e8, ab1c416d2377cdc16123ef521aac4da1c468c3d4, 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Linux kernel to b15c79fca28060fd9c7e77f2c3ebc4ba023974e8, ab1c416d2377cdc16123ef521aac4da1c468c3d4, 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 or 0e0d3372a84029da1768c7a4c4601484af5b58a2.
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– |
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by changing the memory allocation to a no-fail approach for the affected code path. Users should update to the patched kernel version once available. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's XFS filesystem was resolved that involved memory allocation failures during online repair operations. Specifically, a failure in allocating memory for new btree blocks could cause block leaks and potentially crash the filesystem repair process. The underlying issue was that the code could not properly undo partial transactions on error, leading to filesystem instability. The fix involved changing the allocation to a no-fail approach for a small reservation object, preventing the failure scenario.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98445 (opens in a new tab)
- git.kernel.org/stable/c/0e0d3372a84029da1768c7a4c4601484af5b58a2 (opens in a new tab)
- git.kernel.org/stable/c/3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 (opens in a new tab)
- git.kernel.org/stable/c/ab1c416d2377cdc16123ef521aac4da1c468c3d4 (opens in a new tab)
- git.kernel.org/stable/c/b15c79fca28060fd9c7e77f2c3ebc4ba023974e8 (opens in a new tab)