nfsd: fix clock domain mismatch in clients_still_reclaiming()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 20b7d86f29d39e8ae19bb29c24ffee70dc385ddf · < f9cec313efb2fd18d962aad738a4892bce806016| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A clock-domain mismatch in the Linux kernel's nfsd can keep an NFS server in its grace period indefinitely. A client can trigger this by sending CLAIM_PREVIOUS OPEN requests, blocking non-reclaim operations for other clients; no user interaction is described.
Operators running Linux NFS servers should check their kernel; affected versions are not specified.