cbcvebase.
CVE-2026-53399
published 2026-07-19

CVE-2026-53399: 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…

PriorityP346critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.51%
40.9th percentile
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).

Affected

17 ranges
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < d788ef40a7517d22c97ab01700e4ae4c611b6f2fd788ef40a7517d22c97ab01700e4ae4c611b6f2f
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 2e0a5d6d62600b8c614d1b55e50ef94035d6adf92e0a5d6d62600b8c614d1b55e50ef94035d6adf9
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 7bbb7ce74051c8be4b69ff44ce3db370600dae617bbb7ce74051c8be4b69ff44ce3db370600dae61
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 48a586e382e4db1dbf958d44b63e081df5f8ed0448a586e382e4db1dbf958d44b63e081df5f8ed04
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < d369e5edfaaf83a448016e2f1da392b2174be801d369e5edfaaf83a448016e2f1da392b2174be801
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 83c2b7797742339bb768f83935f7ca33950db13883c2b7797742339bb768f83935f7ca33950db138
linuxlinux>= c5c707f96fc9a6e5a57ca5baac892673270abe3d < 30d55c8aabb261bc3f427d6b9aae7ef6206063f930d55c8aabb261bc3f427d6b9aae7ef6206063f9
linuxlinux_kernel——
linuxlinux_kernel>= 4.0 < 5.10.2615.10.261
linuxlinux_kernel>= 5.11 < 5.15.2125.15.212
linuxlinux_kernel>= 5.16 < 6.1.1786.1.178
linuxlinux_kernel>= 6.13 < 6.18.396.18.39
linuxlinux_kernel>= 6.19 < 7.1.37.1.3
linuxlinux_kernel>= 6.2 < 6.6.1456.6.145
linuxlinux_kernel>= 6.7 < 6.12.966.12.96

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.