Answer in brief
CVE-2025-38012 records a Unknown severity vulnerability in sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator. 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 | >=650ba21b131ed1f8ee57826b2c6295a3be221132 <0102989af4c334d1d98b2a0fd4d61a5152e39b72 || >=650ba21b131ed1f8ee57826b2c6295a3be221132 <255dd31bfc4a67a19b1fc2cd130a50284dadfe3a || >=650ba21b131ed1f8ee57826b2c6295a3be221132 <428dc9fc0873989d73918d4a9cc22745b7bbc799 | 0102989af4c334d1d98b2a0fd4d61a5152e39b72, 255dd31bfc4a67a19b1fc2cd130a50284dadfe3a, 428dc9fc0873989d73918d4a9cc22745b7bbc799 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jun 18, 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: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator BPF programs may call next() and destroy() on BPF iterators even after new() returns an error value (e.g. bpf_for_each() macro ignores error returns from new()). bpf_iter_scx_dsq_new() could leave the iterator in an uninitialized state after an error return causing bpf_iter_scx_dsq_next() to dereference garbage data. Make bpf_iter_scx_dsq_new() always clear $kit->dsq so that next() and destroy() become noops.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38012 records a Unknown severity vulnerability in sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator. 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 | >=650ba21b131ed1f8ee57826b2c6295a3be221132 <0102989af4c334d1d98b2a0fd4d61a5152e39b72 || >=650ba21b131ed1f8ee57826b2c6295a3be221132 <255dd31bfc4a67a19b1fc2cd130a50284dadfe3a || >=650ba21b131ed1f8ee57826b2c6295a3be221132 <428dc9fc0873989d73918d4a9cc22745b7bbc799 | 0102989af4c334d1d98b2a0fd4d61a5152e39b72, 255dd31bfc4a67a19b1fc2cd130a50284dadfe3a, 428dc9fc0873989d73918d4a9cc22745b7bbc799 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jun 18, 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: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator BPF programs may call next() and destroy() on BPF iterators even after new() returns an error value (e.g. bpf_for_each() macro ignores error returns from new()). bpf_iter_scx_dsq_new() could leave the iterator in an uninitialized state after an error return causing bpf_iter_scx_dsq_next() to dereference garbage data. Make bpf_iter_scx_dsq_new() always clear $kit->dsq so that next() and destroy() become noops.
Quoted source text, attributed separately from HOL analysis.