CVE-2025-37893
published 2025-04-18CVE-2025-37893: 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…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.25%
16.0th percentile
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.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.12.25-1 (forky) | linux 6.12.25-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 5dc615520c4dfb358245680f1904bad61116648e < b3ffad2f02db4aace6799fe0049508b8925eae45 | b3ffad2f02db4aace6799fe0049508b8925eae45 |
| linux | linux | >= 5dc615520c4dfb358245680f1904bad61116648e < 205a2182c51ffebaef54d643e3745e720cded08b | 205a2182c51ffebaef54d643e3745e720cded08b |
| linux | linux | >= 5dc615520c4dfb358245680f1904bad61116648e < c74d95a5679741ef428974ab788f5b0758dc78ae | c74d95a5679741ef428974ab788f5b0758dc78ae |
| linux | linux | >= 5dc615520c4dfb358245680f1904bad61116648e < 48b904de2408af5f936f0e03f48dfcddeab58aa0 | 48b904de2408af5f936f0e03f48dfcddeab58aa0 |
| linux | linux | >= 5dc615520c4dfb358245680f1904bad61116648e < 7e2586991e36663c9bc48c828b83eab180ad30a9 | 7e2586991e36663c9bc48c828b83eab180ad30a9 |
| linux | linux_kernel | >= 0 < 6.12.25-1 | 6.12.25-1 |
| linux | linux_kernel | >= 0 < 6.12.25-1 | 6.12.25-1 |
| linux | linux_kernel | >= 6.1 < 6.1.134 | 6.1.134 |
| linux | linux_kernel | >= 6.13 < 6.13.11 | 6.13.11 |
| linux | linux_kernel | >= 6.14 < 6.14.2 | 6.14.2 |
| linux | linux_kernel | >= 6.2 < 6.6.87 | 6.6.87 |
| linux | linux_kernel | >= 6.7 < 6.12.23 | 6.12.23 |
| msrc | azl3_kernel_6.6.85.1-4_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.92.2-1_on_azure_linux_3.0 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2025-37893: In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix off-by-one error in build_prologue() Vincent reported that run
osv·2025-04-18·CVSS 5.5
CVE-2025-37893 [MEDIUM] CVE-2025-37893: In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix off-by-one error in build_prologue() Vincent reported that run
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.
GHSA
GHSA-3xjw-75cj-9fvw: In the Linux kernel, the following vulnerability has been resolved:
LoongArch: BPF: Fix off-by-one error in build_prologue()
Vincent reported that r
ghsa_unreviewed·2025-04-18
CVE-2025-37893 [MEDIUM] CWE-193 GHSA-3xjw-75cj-9fvw: In the Linux kernel, the following vulnerability has been resolved:
LoongArch: BPF: Fix off-by-one error in build_prologue()
Vincent reported that r
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.
Red Hat
kernel: LoongArch: BPF: Fix off-by-one error in build_prologue()
vendor_redhat·2025-04-18·CVSS 5.5
CVE-2025-37893 [MEDIUM] CWE-193 kernel: LoongArch: BPF: Fix off-by-one error in build_prologue()
kernel: LoongArch: BPF: Fix off-by-one error in build_prologue()
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.
Pac
Microsoft
LoongArch: BPF: Fix off-by-one error in build_prologue()
vendor_msrc·2025-04-08·CVSS 5.5
CVE-2025-37893 [MEDIUM] LoongArch: BPF: Fix off-by-one error in build_prologue()
LoongArch: BPF: Fix off-by-one error in build_prologue()
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://lear
Debian
CVE-2025-37893: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
vendor_debian·2025·CVSS 5.5
CVE-2025-37893 [MEDIUM] CVE-2025-37893: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
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.
Scope: local
bookworm: open
bullseye: resolved
forky: resolved (fixed
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/205a2182c51ffebaef54d643e3745e720cded08bhttps://git.kernel.org/stable/c/48b904de2408af5f936f0e03f48dfcddeab58aa0https://git.kernel.org/stable/c/7e2586991e36663c9bc48c828b83eab180ad30a9https://git.kernel.org/stable/c/b3ffad2f02db4aace6799fe0049508b8925eae45https://git.kernel.org/stable/c/c74d95a5679741ef428974ab788f5b0758dc78ae
2025-04-18
Published