Answer in brief
CVE-2026-89639 records a High severity (CVSS 7.1) vulnerability in cifs: use cifs_invalidate_cache() in cifs_do_truncate() for O_TRUNC. 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.
CVSS is 7.1. 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 | >=efbcecdecefc26fa062c0e8210533ccad7d6bd4a <8b9b10fe5b8b492b27b9f4546742ea541a650213 || >=fa724e235cfdb0fb0bb427d0f9dfe864ae27403e <81fc3868a7f726980ff845c1d0d271051e5f0f45 || >=fa724e235cfdb0fb0bb427d0f9dfe864ae27403e <364b183230586a62660a7280c1eb20138338eeb5 || 6838bcac954487cc0a3c8a4ee1b3a3a30e244dc9 || 75640976cf474eb41682a13f2dbe9534ac26ca50 || 3513f3931c579ba2a715784c6dedc59e0d9282ee || >=6.18.44 <6.18.50 || >=6.12.105 <6.13 || >=7.1.8 <7.2 | 8b9b10fe5b8b492b27b9f4546742ea541a650213, 81fc3868a7f726980ff845c1d0d271051e5f0f45, 364b183230586a62660a7280c1eb20138338eeb5, 6.18.50, 6.13, 7.2 |
| Linux/Linuxgeneric | 7.2 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: cifs: use cifs_invalidate_cache() in cifs_do_truncate() for O_TRUNC cifs_do_truncate() is invoked from cifs_open() without i_rwsem, so it cannot use cifs_resize_file_locked() to perform a proper fscache cookie resize. Instead, add cifs_invalidate_cache() after cifs_setsize(). cifs_invalidate_cache() calls fscache_invalidate(), which works without holding i_rwsem: it unconditionally increments inval_counter and sets FSCACHE_COOKIE_NO_DATA_TO_READ, ensuring that stale cached data is not served once the cookie is later activated by fscache_use_cookie(). Truncation to zero leaves no valid cached data, making invalidation the correct semantic here.
Quoted source text, attributed separately from HOL analysis.