Answer in brief
CVE-2026-53394 records a Unknown severity vulnerability in nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=23df17788c6212809848f836b10c4f85b16843a5 <c9aefb2b5f11337c9202c5bd0c45d71198449718 || >=23df17788c6212809848f836b10c4f85b16843a5 <017a6150106b054cc84d1b0582d97bd3a74d4281 || >=23df17788c6212809848f836b10c4f85b16843a5 <a10bf67fe06469a71a401f72f328237345d553c0 || >=23df17788c6212809848f836b10c4f85b16843a5 <57aee7a35bb12753057c5b65d72d1f46c0e95b07 | c9aefb2b5f11337c9202c5bd0c45d71198449718, 017a6150106b054cc84d1b0582d97bd3a74d4281, a10bf67fe06469a71a401f72f328237345d553c0, 57aee7a35bb12753057c5b65d72d1f46c0e95b07 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53394 records a Unknown severity vulnerability in nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=23df17788c6212809848f836b10c4f85b16843a5 <c9aefb2b5f11337c9202c5bd0c45d71198449718 || >=23df17788c6212809848f836b10c4f85b16843a5 <017a6150106b054cc84d1b0582d97bd3a74d4281 || >=23df17788c6212809848f836b10c4f85b16843a5 <a10bf67fe06469a71a401f72f328237345d553c0 || >=23df17788c6212809848f836b10c4f85b16843a5 <57aee7a35bb12753057c5b65d72d1f46c0e95b07 | c9aefb2b5f11337c9202c5bd0c45d71198449718, 017a6150106b054cc84d1b0582d97bd3a74d4281, a10bf67fe06469a71a401f72f328237345d553c0, 57aee7a35bb12753057c5b65d72d1f46c0e95b07 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.