Answer in brief
CVE-2026-52973 records a High severity (CVSS 7.8) vulnerability in futex: Drop CLONE_THREAD requirement for private default hash alloc. 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.
Answer in brief
CVE-2026-52973 records a High severity (CVSS 7.8) vulnerability in futex: Drop CLONE_THREAD requirement for private default hash alloc. 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.
CVSS is 7.8. 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 | >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <1dcd36420af2da5bd59306dba9caf78e3d248b1d || >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <974ac49a9a068b0591a59f65c63eb06579a13091 || >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <ee9dce44362b2d8132c32964656ab6dff7dfbc6a | 1dcd36420af2da5bd59306dba9caf78e3d248b1d, 974ac49a9a068b0591a59f65c63eb06579a13091, ee9dce44362b2d8132c32964656ab6dff7dfbc6a |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... where the +1 bias can end up on a percpu counter that mm->futex_ref no longer points at. Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding vfork keeps the existing paths untouched (no overhead), and we can't race in the first place: either the parent is suspended and the child runs alone, or mm->futex_ref is already allocated from an earlier CLONE_VM.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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 | >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <1dcd36420af2da5bd59306dba9caf78e3d248b1d || >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <974ac49a9a068b0591a59f65c63eb06579a13091 || >=d9b05321e21e4b218de4ce8a590bf375f58b6346 <ee9dce44362b2d8132c32964656ab6dff7dfbc6a | 1dcd36420af2da5bd59306dba9caf78e3d248b1d, 974ac49a9a068b0591a59f65c63eb06579a13091, ee9dce44362b2d8132c32964656ab6dff7dfbc6a |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... where the +1 bias can end up on a percpu counter that mm->futex_ref no longer points at. Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding vfork keeps the existing paths untouched (no overhead), and we can't race in the first place: either the parent is suspended and the child runs alone, or mm->futex_ref is already allocated from an earlier CLONE_VM.
Quoted source text, attributed separately from HOL analysis.