Answer in brief
CVE-2026-89685 records a High severity (CVSS 7.5) vulnerability in nfsd: fix clock domain mismatch in clients_still_reclaiming(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), 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.5. 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), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <f9cec313efb2fd18d962aad738a4892bce806016 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <9843649196221152b6e5d138a3ce859bdaae1d96 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <09ea3eb9a518565f5bca386e81b993ed8825f5e8 | f9cec313efb2fd18d962aad738a4892bce806016, 9843649196221152b6e5d138a3ce859bdaae1d96, 09ea3eb9a518565f5bca386e81b993ed8825f5e8 |
| Linux/Linuxgeneric | 5.6 | Not reported |
| Linux/Linuxgeneric | >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <e92e80c5b043108029bc729b30d12c37158fb9cb || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <f9cec313efb2fd18d962aad738a4892bce806016 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <9843649196221152b6e5d138a3ce859bdaae1d96 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <09ea3eb9a518565f5bca386e81b993ed8825f5e8 | e92e80c5b043108029bc729b30d12c37158fb9cb, f9cec313efb2fd18d962aad738a4892bce806016, 9843649196221152b6e5d138a3ce859bdaae1d96, 09ea3eb9a518565f5bca386e81b993ed8825f5e8 |
| Linux/Linuxgeneric | >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <04c3e4456fe76e8d7c94171009df3165c3262c51 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <e92e80c5b043108029bc729b30d12c37158fb9cb || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <f9cec313efb2fd18d962aad738a4892bce806016 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <9843649196221152b6e5d138a3ce859bdaae1d96 || >=20b7d86f29d39e8ae19bb29c24ffee70dc385ddf <09ea3eb9a518565f5bca386e81b993ed8825f5e8 | 04c3e4456fe76e8d7c94171009df3165c3262c51, e92e80c5b043108029bc729b30d12c37158fb9cb, f9cec313efb2fd18d962aad738a4892bce806016, 9843649196221152b6e5d138a3ce859bdaae1d96, 09ea3eb9a518565f5bca386e81b993ed8825f5e8 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 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: nfsd: fix clock domain mismatch in clients_still_reclaiming() clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline. This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients. Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.
Quoted source text, attributed separately from HOL analysis.