Answer in brief
CVE-2026-98117 records a Unknown severity vulnerability in cachefiles: Fix potential UAF/KASAN warning. 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 | >=229105e5cfd9832a9ef1368c96e0098ec3a5fbf0 <68d459e6e609c31f96a203dd6eec60c634f155e1 || >=229105e5cfd9832a9ef1368c96e0098ec3a5fbf0 <93488ea378b4427598cace558236c110515d743b || >=229105e5cfd9832a9ef1368c96e0098ec3a5fbf0 <a67632c8c2688d6e0091529bcefe54bc5ee80e9b | 68d459e6e609c31f96a203dd6eec60c634f155e1, 93488ea378b4427598cace558236c110515d743b, a67632c8c2688d6e0091529bcefe54bc5ee80e9b |
| Linux/Linuxgeneric | 6.14 | 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: cachefiles: Fix potential UAF/KASAN warning Currently, trace_cachefiles_coherency() is being passed a pointer to a __be64 lain over the coherency data in struct cachefiles_xattr so that it can display the first 8 bytes. However, the data is of variable length and could even be 0 bytes. This could lead to a UAF or KASAN warning. Fix this by making sure the buffer has room for at least 8 bytes and that those 8 bytes are pre-cleared. Further, those bytes are not 8-byte aligned, so fix the tracepoint to extract the data as four 2-byte words (they are 2-byte aligned) and reassemble the __be64. The compiler will convert this into a single 8-byte load where the CPU supports it.
Quoted source text, attributed separately from HOL analysis.