CVE-2025-37893

published 18 Apr 2025 · updated 5 Aug 2026

LoongArch: BPF: Fix off-by-one error in build_prologue()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 205a2182c51ffebaef54d643e3745e720cded08b, Kernel 48b904de2408af5f936f0e03f48dfcddeab58aa0, Kernel 7e2586991e36663c9bc48c828b83eab180ad30a9 and 2 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.1, >=5dc615520c4dfb358245680f1904bad61116648e <205a2182c51ffebaef54d643e3745e720cded08b, >=5dc615520c4dfb358245680f1904bad61116648e <48b904de2408af5f936f0e03f48dfcddeab58aa0, >=5dc615520c4dfb358245680f1904bad61116648e <7e2586991e36663c9bc48c828b83eab180ad30a9, >=5dc615520c4dfb358245680f1904bad61116648e <b3ffad2f02db4aace6799fe0049508b8925eae45, >=5dc615520c4dfb358245680f1904bad61116648e <c74d95a5679741ef428974ab788f5b0758dc78ae205a2182c51ffebaef54d643e3745e720cded08b, 48b904de2408af5f936f0e03f48dfcddeab58aa0, 7e2586991e36663c9bc48c828b83eab180ad30a9, b3ffad2f02db4aace6799fe0049508b8925eae45, c74d95a5679741ef428974ab788f5b0758dc78ae

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-37893 severity on Zeptric[![CVE-2025-37893](https://zeptric.io/badge/cve/CVE-2025-37893.svg)](https://zeptric.io/cve/CVE-2025-37893)