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-38723LoongArch: BPF: Fix jump offset calculation in tailcall

Description

In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix jump offset calculation in tailcall The extra pass of bpf_int_jit_compile() skips JIT context initialization which essentially skips offset calculation leaving out_offset = -1, so the jmp_offset in emit_bpf_tail_call is calculated by "#define jmp_offset (out_offset - (cur_offset))" is a negative number, which is wrong. The final generated assembly are as follow. 54: bgeu $a2, $t1, -8 # 0x0000004c 58: addi.d $a6, $s5, -1 5c: bltz $a6, -16 # 0x0000004c 60: alsl.d $t2, $a2, $a1, 0x3 64: ld.d $t2, $t2, 264 68: beq $t2, $zero, -28 # 0x0000004c Before apply this patch, the follow test case will reveal soft lock issues. cd tools/testing/selftests/bpf/ ./test_progs --allow=tailcalls/tailcall_bpf2bpf_1 dmesg: watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [test_progs:25056]

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 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-38723, by who scored it
Scored byCVSSScoreVector
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.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 1a782fa32e644aa9fbae6c8488f3e61221ac96e1
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 17c010fe45def335fe03a0718935416b04c7f349
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < f83d469e16bb1f75991ca67c56786fb2aaa42bea
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < f2b5e50cc04d7a049b385bc1c93b9cbf5f10c94f
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < 9262e3e04621558e875eb5afb5e726b648cd5949
    • affected 5dc615520c4dfb358245680f1904bad61116648e – < cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .