Menu

Star on GitHub · 3.2k

CVE-2026-53399

9.8 · CRITICAL

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_cycli…

Published Jul 19, 2026CWE-476EPSS 0.54%

Overview

CVE-2026-53399 is a critical-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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,

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-53399?

CVE-2026-53399 is a critical-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-53399?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-53399?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53399?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53399 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all