Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-53399

nfsd: release layout stid on setlease failure

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

In the Linux kernel, the following vulnerability has been resolved: nfsd: release layout stid on setlease failure nfs4_alloc_stid() publishes the new stid into cl->cl_stateids via idr_alloc_cyclic() under cl_lock before returning to nfsd4_alloc_layout_stateid(). When nfsd4_layout_setlease() then fails, the error path frees the layout stateid directly with kmem_cache_free() without ever calling idr_remove(), leaving the IDR slot pointing at freed slab memory. Any subsequent IDR walker (states_show, client teardown) dereferences the dangling pointer. The correct teardown for an IDR-published stid is nfs4_put_stid(), which removes the IDR slot under cl_lock, dispatches sc_free (nfsd4_free_layout_stateid) to release ls->ls_file via nfsd4_close_layout(), and drops the nfs4_file reference in its tail. A second issue blocks that switch: nfsd4_free_layout_stateid() unconditionally inspects ls->ls_fence_work via delayed_work_pending() under ls_lock, but INIT_DELAYED_WORK(&ls->ls_fence_work, ...) currently runs only after the setlease call. On the setlease-failure path the destructor would touch an uninitialized delayed_work. nfsd4_alloc_layout_stateid() nfs4_alloc_stid() /* idr_alloc_cyclic under cl_lock */ nfsd4_layout_setlease() /* fails */ nfs4_put_stid() nfsd4_free_layout_stateid() delayed_work_pending(&ls->ls_fence_work) /* needs INIT */ nfsd4_close_layout() /* nfsd_file_put(ls->ls_file) */ put_nfs4_file() Fix by hoisting the ls_fenced / ls_fence_delay / INIT_DELAYED_WORK initialization above the nfsd4_layout_setlease() call, and replace the manual nfsd_file_put + put_nfs4_file + kmem_cache_free cleanup with a single nfs4_put_stid(stp).

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in d788ef40a7517d22c97ab01700e4ae4c611b6f2f; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 2e0a5d6d62600b8c614d1b55e50ef94035d6adf9; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 7bbb7ce74051c8be4b69ff44ce3db370600dae61; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 48a586e382e4db1dbf958d44b63e081df5f8ed04; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in d369e5edfaaf83a448016e2f1da392b2174be801; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 83c2b7797742339bb768f83935f7ca33950db138; From c5c707f96fc9a6e5a57ca5baac892673270abe3d · fixed in 30d55c8aabb261bc3f427d6b9aae7ef6206063f9

  • Linux Linux

    4.0

  • KernelLinux

    From 4.0.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.3

References 8

git.kernel.org