CVE-2026-53394

published 19 Jul 2026 · updated 19 Oct 2026

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

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 017a6150106b054cc84d1b0582d97bd3a74d4281, Kernel 57aee7a35bb12753057c5b65d72d1f46c0e95b07, Kernel a10bf67fe06469a71a401f72f328237345d553c0 and 1 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.10, >=23df17788c6212809848f836b10c4f85b16843a5 <017a6150106b054cc84d1b0582d97bd3a74d4281, >=23df17788c6212809848f836b10c4f85b16843a5 <57aee7a35bb12753057c5b65d72d1f46c0e95b07, >=23df17788c6212809848f836b10c4f85b16843a5 <a10bf67fe06469a71a401f72f328237345d553c0, >=23df17788c6212809848f836b10c4f85b16843a5 <c9aefb2b5f11337c9202c5bd0c45d71198449718017a6150106b054cc84d1b0582d97bd3a74d4281, 57aee7a35bb12753057c5b65d72d1f46c0e95b07, a10bf67fe06469a71a401f72f328237345d553c0, c9aefb2b5f11337c9202c5bd0c45d71198449718

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53394 severity on Zeptric[![CVE-2026-53394](https://zeptric.io/badge/cve/CVE-2026-53394.svg)](https://zeptric.io/cve/CVE-2026-53394)