In the Linux kernel, the following vulnerability has been resolved: nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race When… (CVE-2026-53394)
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.
AI Analysis
Technical Summary
The Linux kernel's nfsd component had a vulnerability (CVE-2026-53394) where the function find_or_alloc_open_stateowner() could leak memory due to a race condition. When encountering an unconfirmed owner, the code would release the openowner and set the pointer to NULL but then proceed to allocate a new stateowner unconditionally, overwriting the pointer to a previously allocated object and causing a memory leak. This race requires two concurrent NFSv4.0 OPEN threads with the same owner string and a concurrent insertion of a new unconfirmed owner between retry attempts. The fix adds a retry jump to reuse the already allocated object, preventing the leak.
Potential Impact
The vulnerability causes a memory leak in the Linux kernel's NFS server under specific race conditions involving concurrent NFSv4.0 OPEN requests with the same owner string. While the window for exploitation is narrow, repeated triggering under adversarial conditions can lead to resource exhaustion or degraded service availability due to leaked memory allocations.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by changing the retry logic to reuse allocated objects and prevent memory leaks. Users should apply the official kernel updates or patches that include this fix. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisory for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race When… (CVE-2026-53394)
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.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's nfsd component had a vulnerability (CVE-2026-53394) where the function find_or_alloc_open_stateowner() could leak memory due to a race condition. When encountering an unconfirmed owner, the code would release the openowner and set the pointer to NULL but then proceed to allocate a new stateowner unconditionally, overwriting the pointer to a previously allocated object and causing a memory leak. This race requires two concurrent NFSv4.0 OPEN threads with the same owner string and a concurrent insertion of a new unconfirmed owner between retry attempts. The fix adds a retry jump to reuse the already allocated object, preventing the leak.
Potential Impact
The vulnerability causes a memory leak in the Linux kernel's NFS server under specific race conditions involving concurrent NFSv4.0 OPEN requests with the same owner string. While the window for exploitation is narrow, repeated triggering under adversarial conditions can lead to resource exhaustion or degraded service availability due to leaked memory allocations.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by changing the retry logic to reuse allocated objects and prevent memory leaks. Users should apply the official kernel updates or patches that include this fix. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisory for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3gwr-8cwh-87h2
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53394"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ad2a4a8d59891325c2
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/19/2026, 20:24:50 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.