Answer in brief
CVE-2025-38306 records a Unknown severity vulnerability in fs/fhandle.c: fix a race in call of has_locked_children(). 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 | >=620c266f394932e5decc4b34683a75dfc59dc2f4 <6482c3dccbfb8d20e2856ce67c75856859930b3f || >=620c266f394932e5decc4b34683a75dfc59dc2f4 <287c7d34eedd37af1272dfb3b6e8656f4f026424 || >=620c266f394932e5decc4b34683a75dfc59dc2f4 <1f282cdc1d219c4a557f7009e81bc792820d9d9a | 6482c3dccbfb8d20e2856ce67c75856859930b3f, 287c7d34eedd37af1272dfb3b6e8656f4f026424, 1f282cdc1d219c4a557f7009e81bc792820d9d9a |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jul 10, 2025
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: fs/fhandle.c: fix a race in call of has_locked_children() may_decode_fh() is calling has_locked_children() while holding no locks. That's an oopsable race... The rest of the callers are safe since they are holding namespace_sem and are guaranteed a positive refcount on the mount in question. Rename the current has_locked_children() to __has_locked_children(), make it static and switch the fs/namespace.c users to it. Make has_locked_children() a wrapper for __has_locked_children(), calling the latter under read_seqlock_excl(&mount_lock).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38306 records a Unknown severity vulnerability in fs/fhandle.c: fix a race in call of has_locked_children(). 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 | >=620c266f394932e5decc4b34683a75dfc59dc2f4 <6482c3dccbfb8d20e2856ce67c75856859930b3f || >=620c266f394932e5decc4b34683a75dfc59dc2f4 <287c7d34eedd37af1272dfb3b6e8656f4f026424 || >=620c266f394932e5decc4b34683a75dfc59dc2f4 <1f282cdc1d219c4a557f7009e81bc792820d9d9a | 6482c3dccbfb8d20e2856ce67c75856859930b3f, 287c7d34eedd37af1272dfb3b6e8656f4f026424, 1f282cdc1d219c4a557f7009e81bc792820d9d9a |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jul 10, 2025
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: fs/fhandle.c: fix a race in call of has_locked_children() may_decode_fh() is calling has_locked_children() while holding no locks. That's an oopsable race... The rest of the callers are safe since they are holding namespace_sem and are guaranteed a positive refcount on the mount in question. Rename the current has_locked_children() to __has_locked_children(), make it static and switch the fs/namespace.c users to it. Make has_locked_children() a wrapper for __has_locked_children(), calling the latter under read_seqlock_excl(&mount_lock).
Quoted source text, attributed separately from HOL analysis.