Answer in brief
CVE-2025-37893 records a Unknown severity vulnerability in LoongArch: BPF: Fix off-by-one error in build_prologue(). 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 | >=5dc615520c4dfb358245680f1904bad61116648e <b3ffad2f02db4aace6799fe0049508b8925eae45 || >=5dc615520c4dfb358245680f1904bad61116648e <205a2182c51ffebaef54d643e3745e720cded08b || >=5dc615520c4dfb358245680f1904bad61116648e <c74d95a5679741ef428974ab788f5b0758dc78ae || >=5dc615520c4dfb358245680f1904bad61116648e <48b904de2408af5f936f0e03f48dfcddeab58aa0 || >=5dc615520c4dfb358245680f1904bad61116648e <7e2586991e36663c9bc48c828b83eab180ad30a9 | b3ffad2f02db4aace6799fe0049508b8925eae45, 205a2182c51ffebaef54d643e3745e720cded08b, c74d95a5679741ef428974ab788f5b0758dc78ae, 48b904de2408af5f936f0e03f48dfcddeab58aa0, 7e2586991e36663c9bc48c828b83eab180ad30a9 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Apr 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: LoongArch: BPF: Fix off-by-one error in build_prologue() Vincent reported that running BPF progs with tailcalls on LoongArch causes kernel hard lockup. Debugging the issues shows that the JITed image missing a jirl instruction at the end of the epilogue. There are two passes in JIT compiling, the first pass set the flags and the second pass generates JIT code based on those flags. With BPF progs mixing bpf2bpf and tailcalls, build_prologue() generates N insns in the first pass and then generates N+1 insns in the second pass. This makes epilogue_offset off by one and we will jump to some unexpected insn and cause lockup. Fix this by inserting a nop insn.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37893 records a Unknown severity vulnerability in LoongArch: BPF: Fix off-by-one error in build_prologue(). 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 | >=5dc615520c4dfb358245680f1904bad61116648e <b3ffad2f02db4aace6799fe0049508b8925eae45 || >=5dc615520c4dfb358245680f1904bad61116648e <205a2182c51ffebaef54d643e3745e720cded08b || >=5dc615520c4dfb358245680f1904bad61116648e <c74d95a5679741ef428974ab788f5b0758dc78ae || >=5dc615520c4dfb358245680f1904bad61116648e <48b904de2408af5f936f0e03f48dfcddeab58aa0 || >=5dc615520c4dfb358245680f1904bad61116648e <7e2586991e36663c9bc48c828b83eab180ad30a9 | b3ffad2f02db4aace6799fe0049508b8925eae45, 205a2182c51ffebaef54d643e3745e720cded08b, c74d95a5679741ef428974ab788f5b0758dc78ae, 48b904de2408af5f936f0e03f48dfcddeab58aa0, 7e2586991e36663c9bc48c828b83eab180ad30a9 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Apr 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: LoongArch: BPF: Fix off-by-one error in build_prologue() Vincent reported that running BPF progs with tailcalls on LoongArch causes kernel hard lockup. Debugging the issues shows that the JITed image missing a jirl instruction at the end of the epilogue. There are two passes in JIT compiling, the first pass set the flags and the second pass generates JIT code based on those flags. With BPF progs mixing bpf2bpf and tailcalls, build_prologue() generates N insns in the first pass and then generates N+1 insns in the second pass. This makes epilogue_offset off by one and we will jump to some unexpected insn and cause lockup. Fix this by inserting a nop insn.
Quoted source text, attributed separately from HOL analysis.