CVE-2026-53394: Linux kernel · nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race
Source GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in c9aefb2b5f11337c9202c5bd0c45d71198449718 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c9aefb2b5f11337c9202c5bd0c45d71198449718, a10bf67fe06469a71a401f72f328237345d553c0, 57aee7a35bb12753057c5b65d72d1f46c0e95b07 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to c9aefb2b5f11337c9202c5bd0c45d71198449718, a10bf67fe06469a71a401f72f328237345d553c0, 57aee7a35bb12753057c5b65d72d1f46c0e95b07 or 017a6150106b054cc84d1b0582d97bd3a74d4281.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
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.
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-53394 (opens in a new tab)
- git.kernel.org/stable/c/017a6150106b054cc84d1b0582d97bd3a74d4281 (opens in a new tab)
- git.kernel.org/stable/c/57aee7a35bb12753057c5b65d72d1f46c0e95b07 (opens in a new tab)
- git.kernel.org/stable/c/a10bf67fe06469a71a401f72f328237345d553c0 (opens in a new tab)
- git.kernel.org/stable/c/c9aefb2b5f11337c9202c5bd0c45d71198449718 (opens in a new tab)