Answer in brief
CVE-2026-98445 records a Unknown severity vulnerability in xfs: don't let memory failures leak blocks and kill repairs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=be408417630427984a1fddd069f30b245793234c <3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 || >=be408417630427984a1fddd069f30b245793234c <b15c79fca28060fd9c7e77f2c3ebc4ba023974e8 || >=be408417630427984a1fddd069f30b245793234c <0e0d3372a84029da1768c7a4c4601484af5b58a2 || >=be408417630427984a1fddd069f30b245793234c <ab1c416d2377cdc16123ef521aac4da1c468c3d4 | 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50, b15c79fca28060fd9c7e77f2c3ebc4ba023974e8, 0e0d3372a84029da1768c7a4c4601484af5b58a2, ab1c416d2377cdc16123ef521aac4da1c468c3d4 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: xfs: don't let memory failures leak blocks and kill repairs LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down. However, the new btree space reservation object isn't that big (~48 bytes). Let's just do a NOFAIL allocation and the problem goes away.
Quoted source text, attributed separately from HOL analysis.