CVE-2025-38723 json
LoongArch: BPF: Fix jump offset calculation in tailcall
published 2025-09-04 14 mo ago modified 2026-10-19 20 d ago also EUVD-2025-26746
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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]
Patch / fix
- Linux Linux 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2, 6.17
- Siemens SIMATIC CN 4100 V5.0
- linux Debian 12 6.1.153-1
- linux Debian 13 6.12.43-1
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38723
- git.kernel.org/stable/c/1a782fa32e644aa9fbae6c8488f3e61221ac96e1 commit
- git.kernel.org/stable/c/17c010fe45def335fe03a0718935416b04c7f349 commit
- git.kernel.org/stable/c/f83d469e16bb1f75991ca67c56786fb2aaa42bea commit
- git.kernel.org/stable/c/f2b5e50cc04d7a049b385bc1c93b9cbf5f10c94f commit
- git.kernel.org/stable/c/9262e3e04621558e875eb5afb5e726b648cd5949 commit
- git.kernel.org/stable/c/cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38723 updated
kernel: LoongArch: BPF: Fix jump offset calculation in tailcall
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
cisa ICSA-26-134-10 updated cvss 5.5
Siemens SIMATIC
-
Siemens SIMATIC CN 4100 < 5.0affected: fixed in V5.0 support.industry.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
- Siemens SIMATIC CN 4100
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/1a782fa32e644aa9fbae6c8488f3e61221ac96e1
patch
-
git.kernel.org
/stable/c/17c010fe45def335fe03a0718935416b04c7f349
patch
-
git.kernel.org
/stable/c/f83d469e16bb1f75991ca67c56786fb2aaa42bea
patch
-
git.kernel.org
/stable/c/f2b5e50cc04d7a049b385bc1c93b9cbf5f10c94f
patch
-
git.kernel.org
/stable/c/9262e3e04621558e875eb5afb5e726b648cd5949
patch
-
git.kernel.org
/stable/c/cd39d9e6b7e4c58fa77783e7aedf7ada51d02ea3
patch
-
lists.debian.org
/debian-lts-announce/2025/10/msg00008.html
mailing-list, third-party-advisory
- cert-portal.siemens.com /productcert/html/ssa-032379.html
Sources
- CVE List CVE-2025-38723
- NVD CVE-2025-38723
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.