Answer in brief
CVE-2026-80532 records a Unknown severity vulnerability in xfs: fix another iunlink infinite loop bug in online fsck. 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 | >=ab97f4b1c030750f2475bf4da8a9554d02206640 <24aec8c88539a382355761a9b924046885b6be40 || >=ab97f4b1c030750f2475bf4da8a9554d02206640 <b6baf0db357fb84f3f3cfd33383a00de71a5a1c3 || >=ab97f4b1c030750f2475bf4da8a9554d02206640 <23690064f235a88a00c04f2e49f36bfb54ae560d || >=ab97f4b1c030750f2475bf4da8a9554d02206640 <6d67c6b99f1fc07c64b97fcbc974c6f1ada7f622 | 24aec8c88539a382355761a9b924046885b6be40, b6baf0db357fb84f3f3cfd33383a00de71a5a1c3, 23690064f235a88a00c04f2e49f36bfb54ae560d, 6d67c6b99f1fc07c64b97fcbc974c6f1ada7f622 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 26, 2026
In the Linux kernel, the following vulnerability has been resolved: xfs: fix another iunlink infinite loop bug in online fsck xrep_iunlink_resolve_bucket is supposed to reconstruct as much of the incore prev and next unlinked list pointers based on what it finds on disk and in memory before we move on to relinking the truly lost inodes back into the unlinked list. However, it's still vulnerable to infinite loops that come in via the next_unlinked pointers. Fix this problem by remembering which inodes we've already seen and checking new agino pointers against that. If a bit is already set, either this is a loop or the inode has nonzero link count. We'll deal with the second case in a subsequent patch.
Quoted source text, attributed separately from HOL analysis.