Answer in brief
CVE-2025-38607 records a Unknown severity vulnerability in bpf: handle jset (if a & b ...) as a jump in CFG computation. 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 | >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <65eb166b8636365ad3d6e36d50a7c5edfe6cc66e || >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <261b30ad1516f4b9edd500aa6e8d6315c8fc109a || >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <3157f7e2999616ac91f4d559a8566214f74000a5 | 65eb166b8636365ad3d6e36d50a7c5edfe6cc66e, 261b30ad1516f4b9edd500aa6e8d6315c8fc109a, 3157f7e2999616ac91f4d559a8566214f74000a5 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 19, 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: bpf: handle jset (if a & b ...) as a jump in CFG computation BPF_JSET is a conditional jump and currently verifier.c:can_jump() does not know about that. This can lead to incorrect live registers and SCC computation. E.g. in the following example: 1: r0 = 1; 2: r2 = 2; 3: if r1 & 0x7 goto +1; 4: exit; 5: r0 = r2; 6: exit; W/o this fix insn_successors(3) will return only (4), a jump to (5) would be missed and r2 won't be marked as alive at (3).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38607 records a Unknown severity vulnerability in bpf: handle jset (if a & b ...) as a jump in CFG computation. 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 | >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <65eb166b8636365ad3d6e36d50a7c5edfe6cc66e || >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <261b30ad1516f4b9edd500aa6e8d6315c8fc109a || >=14c8552db64476ffc27c13dc6652fc0dac31c0ba <3157f7e2999616ac91f4d559a8566214f74000a5 | 65eb166b8636365ad3d6e36d50a7c5edfe6cc66e, 261b30ad1516f4b9edd500aa6e8d6315c8fc109a, 3157f7e2999616ac91f4d559a8566214f74000a5 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 19, 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: bpf: handle jset (if a & b ...) as a jump in CFG computation BPF_JSET is a conditional jump and currently verifier.c:can_jump() does not know about that. This can lead to incorrect live registers and SCC computation. E.g. in the following example: 1: r0 = 1; 2: r2 = 2; 3: if r1 & 0x7 goto +1; 4: exit; 5: r0 = r2; 6: exit; W/o this fix insn_successors(3) will return only (4), a jump to (5) would be missed and r2 won't be marked as alive at (3).
Quoted source text, attributed separately from HOL analysis.