Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37893, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.29% · top 79% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 5dc615520c4dfb358245680f1904bad61116648e – < b3ffad2f02db4aace6799fe0049508b8925eae45
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 205a2182c51ffebaef54d643e3745e720cded08b
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < c74d95a5679741ef428974ab788f5b0758dc78ae
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 48b904de2408af5f936f0e03f48dfcddeab58aa0
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 7e2586991e36663c9bc48c828b83eab180ad30a9
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.6.87 – ≤ 6.6.*
    • unaffected 6.12.23 – ≤ 6.12.*
    • unaffected 6.13.11 – ≤ 6.13.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37893 badge
[![CVE-2025-37893](https://cveledger.app/badge/CVE-2025-37893.svg)](https://cveledger.app/cve/CVE-2025-37893)

Record last updated .