CVE-2026-53394

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

Published Jul 19, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw is in the Linux kernel’s NFSv4.0 server in the routine that allocates open state owners. When an unconfirmed owner is found, the code clears the existing pointer but then continues to allocate a new state owner unconditionally. If a prior allocation still exists from a previous iteration, the pointer to that allocation is overwritten and the previously allocated slab object and its associated owner name buffer leak into uninitialized memory. This is a classic runtime memory‑leak scenario (CWE‑401 and CWE‑772) that allows an attacker to read kernel memory that should remain private. The leak may not directly grant arbitrary code execution, but it can reveal sensitive data or disrupt the NFS service by exhausting memory or corrupting critical bookkeeping structures.

Affected Systems

All Linux kernel implementations that have not merged the upstream fix for CVE‑2026‑53394 are affected, regardless of distribution. The vulnerability resides entirely in the NFSv4.0 server code, so systems that run a vulnerable kernel and expose the NFSv4.0 service are at risk. Specific kernel versions are not enumerated in the CVE data; users should verify whether their installed kernel already includes the patch. Any Linux machine serving NFSv4.0 clients could be impacted, including servers, routers, and embedded devices.

Risk and Exploitability

The CVSS score of 7.5 categorizes this as high severity. The EPSS score of less than 1% and the absence from CISA's KEV catalog suggest that real‑world exploitation is currently unlikely, yet the narrow race condition can be engineered by a malicious NFS client generating repeated OPEN requests with the same owner string. The attack requires no privilege elevation on the client side, making the threat surface larger. If successful, the attacker could continuously leak slices of kernel memory or cause a denial of service by causing repeated allocations to fail or by exhausting memory resources.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a Linux kernel update that includes the CVE‑2026‑53394 fix as soon as it becomes available.
  • If a kernel upgrade is not immediately feasible, consider disabling the NFSv4.0 server or limiting NFSv4.0 client access to trusted hosts.
  • Additionally, monitor the NFS server for anomalous bursts of concurrent OPEN requests, particularly those using the same owner string, as an early indicator of a possible race‑condition exploit.

Generated by OpenCVE AI on August 12, 2026 at 09:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8726-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8727-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-3 Linux kernel (IBM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8800-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
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.
Title nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

  • CWE-772

    Missing Release of Resource after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:07 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Modified
Published
Jul 19, 2026, 12:16 PM
Modified
Oct 19, 2026, 8:19 PM
Severity
Moderate
Public date
Jul 19, 2026, 12:00 AM