CVE-2026-53399nfsd: release layout stid on setlease failure
- 9.8CriticalCVSS base score
- 0.66%Exploitation in 30 daysEPSS · top 48% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
- 40 days later
· 40 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.66% · top 48% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < d788ef40a7517d22c97ab01700e4ae4c611b6f2f
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 2e0a5d6d62600b8c614d1b55e50ef94035d6adf9
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 7bbb7ce74051c8be4b69ff44ce3db370600dae61
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 48a586e382e4db1dbf958d44b63e081df5f8ed04
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < d369e5edfaaf83a448016e2f1da392b2174be801
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 83c2b7797742339bb768f83935f7ca33950db138
- affected c5c707f96fc9a6e5a57ca5baac892673270abe3d – < 30d55c8aabb261bc3f427d6b9aae7ef6206063f9
- affected 4.0
- unaffected < 4.0
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.3 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/d788ef40a7517d22c97ab01700e4ae4c611b6f2f (opens in a new tab)
- https://git.kernel.org/stable/c/2e0a5d6d62600b8c614d1b55e50ef94035d6adf9 (opens in a new tab)
- https://git.kernel.org/stable/c/7bbb7ce74051c8be4b69ff44ce3db370600dae61 (opens in a new tab)
- https://git.kernel.org/stable/c/48a586e382e4db1dbf958d44b63e081df5f8ed04 (opens in a new tab)
- https://git.kernel.org/stable/c/d369e5edfaaf83a448016e2f1da392b2174be801 (opens in a new tab)
- https://git.kernel.org/stable/c/8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd (opens in a new tab)
- https://git.kernel.org/stable/c/83c2b7797742339bb768f83935f7ca33950db138 (opens in a new tab)
- https://git.kernel.org/stable/c/30d55c8aabb261bc3f427d6b9aae7ef6206063f9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45454 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53399)Record last updated .