Answer in brief
CVE-2026-80535 records a Unknown severity vulnerability in xfs: don't double-lock when deleting a self-referential directory. 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 | >=3f31406aef493b3f19020909d29974e28253f91c <17bc347cbdfb125eddac0a815b1f6c1f6eb56676 || >=3f31406aef493b3f19020909d29974e28253f91c <ce2a7006ec5ed88db1b1669124ec85bc1714ccaa || >=3f31406aef493b3f19020909d29974e28253f91c <c575904471570e69bce40fa638365c6c0403e2ff || >=3f31406aef493b3f19020909d29974e28253f91c <5fc643fb86599e29b38e7b2c2680b4b15bf8f772 | 17bc347cbdfb125eddac0a815b1f6c1f6eb56676, ce2a7006ec5ed88db1b1669124ec85bc1714ccaa, c575904471570e69bce40fa638365c6c0403e2ff, 5fc643fb86599e29b38e7b2c2680b4b15bf8f772 |
| 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: don't double-lock when deleting a self-referential directory LOLLM notices that the dirtree scrubber can detect a directory that refers to itself. In this case, it's not correct for the directory tree repair code to try to iolock/ilock both sc->ip and dp, because they're the same inode. Fix this by detecting that corner case and handling it appropriately.
Quoted source text, attributed separately from HOL analysis.