nfsd: fix layout fence worker double-reference race
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 8580571227451384399b3fa53fcde19848c48e5a and Kernel a278d361e0e8f242211891193d56483a7a9f47a8.
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix layout fence worker double-reference race The workqueue core clears WORK_STRUCT_PENDING before the callback is invoked, so delayed_work_pending() in lm_breaker_timedout() can return false while the fence worker is already running. This lets the breaker take a duplicate sc_count reference and schedule a new worker that coalesces with the in-progress one. The extra reference is never put, leaking the layout stateid. Replace the racy delayed_work_pending() check with an ls_fence_inflight boolean set atomically with refcount_inc_not_zero() under ls_lock, and cleared under ls_lock before the final nfs4_put_stid() on the dispose path; the retry path intentionally retains it. Remove the self-rearm mod_delayed_work() at the top of the worker.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=f52792f484ba2316853736856dde19b7e7458861 <8580571227451384399b3fa53fcde19848c48e5a, >=f52792f484ba2316853736856dde19b7e7458861 <a278d361e0e8f242211891193d56483a7a9f47a8 | 8580571227451384399b3fa53fcde19848c48e5a, a278d361e0e8f242211891193d56483a7a9f47a8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket