Answer in brief
CVE-2026-98005 records a Unknown severity vulnerability in erofs: delimit inode_share cache key components. 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 | >=e0bf7d1c074dc4252223ae897560345ccc24100d <16322a67336cfeea0af4b05206ef8d0e0eda55bb || >=e0bf7d1c074dc4252223ae897560345ccc24100d <96bf9831fbf423b8104f7948cd8fe7007ecfb46c | 16322a67336cfeea0af4b05206ef8d0e0eda55bb, 96bf9831fbf423b8104f7948cd8fe7007ecfb46c |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: erofs: delimit inode_share cache key components Previously, inode_share keys were encoded as follows: fingerprint || domain_id It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won't be parsed as part of a domain ID. Change the key encoding as follows: domain_id || '\0' || fingerprint Since domain_id is a NUL-terminated string, this makes the in-memory key indices unambiguous.
Quoted source text, attributed separately from HOL analysis.