Answer in brief
CVE-2026-74596 records a Unknown severity vulnerability in fs,fsverity: remove check for fsverity being enabled in setattr_prepare(). 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 | >=e9734653c523c744f03333ece6ae7a315187f05c <2d2b2ed7bdcc6df4942292318c5455b5e94ba525 || >=e9734653c523c744f03333ece6ae7a315187f05c <d2f96bcb89d36d488a10e3bcf819b98536968286 | 2d2b2ed7bdcc6df4942292318c5455b5e94ba525, d2f96bcb89d36d488a10e3bcf819b98536968286 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
In the Linux kernel, the following vulnerability has been resolved: fs,fsverity: remove check for fsverity being enabled in setattr_prepare() The check that fs-verity is available in the kernel is not necessary here. Filesystems could have fsverity files even without fs-verity enabled. In that case, truncate on fsverity file will succeed, what this check is trying to prevent.
Quoted source text, attributed separately from HOL analysis.