All reports
Low

kernel: nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-53394

Probability of exploitation in the next 30 days: 0.63%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in the Linux kernel's Network File System (NFS) version 4.0 (NFSv4.0) OPEN implementation. A race condition can occur when two NFSv4.0 OPEN threads with the same owner string attempt to open a file, and a concurrent thread inserts a new unconfirmed owner. This can lead to a memory leak where pre-allocated memory for an openowner is not properly released, potentially causing a Denial of Service (DoS) over time due to resource exhaustion.