CVE Catalog

CVE-2026-53394

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.49%

40th percentile - higher than 40% of all known CVEs

Summary

In the Linux kernel NFSD module, a memory leak was found related to pre-allocated openowner structures. The issue occurs in find_or_alloc_open_stateowner() during a race condition with unconfirmed open owners in NFSv4.0.

Risk Assessment

Memory leak may lead to gradual exhaustion of system resources, potentially causing denial of service (DoS) for NFS clients.

Recommendation

Immediately update the Linux kernel to a version containing the fix (commit adding 'goto retry' after setting oo = NULL).

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race When find_or_alloc_open_stateowner() encounters an unconfirmed owner, it calls release_openowner() and sets oo = NULL. Control then falls through past the `if (oo)` guard -- which would have freed any pre-allocated `new` -- and unconditionally executes `new = alloc_stateowner(...)`. If `new` was already allocated on a prior iteration, the pointer is silently overwritten and the previous allocation (slab object + owner name buffer) is leaked. This requires a race: two NFSv4.0 OPEN threads with the same owner string, where a concurrent thread inserts a new unconfirmed owner into the hash between retry iterations. The window is narrow but repeatable under adversarial conditions. Fix by adding `goto retry` after `oo = NULL` so the already-allocated `new` is reused on the next iteration rather than overwritten.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS